Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Upgrade Guide for Terrajet-based Providers #217

Open
ulucinar opened this issue Jan 31, 2022 · 2 comments
Open

Upgrade Guide for Terrajet-based Providers #217

ulucinar opened this issue Jan 31, 2022 · 2 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@ulucinar
Copy link
Collaborator

What problem are you facing?

Currently we only generate one version of a given resource with Terrajet as discussed in #212. We had better clarify the current upgrade approach without multiple versions.

How could Terrajet help solve your problem?

Should we plan for an upgrade guide for Terrajet-based providers?

@ulucinar ulucinar added the enhancement New feature or request label Jan 31, 2022
@muvaf
Copy link
Member

muvaf commented Jan 31, 2022

The ones with non-breaking API changes would be solved with #212 I believe, which are most of them. But I expect to have more breaking changes the more we add manual configurations with external name config which may remove a field from spec, so, probably that would be the scenario where this would be most useful.

@stale
Copy link

stale bot commented Aug 13, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants