Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When moving to a new major version, preserve all default API versions of the previous one #3424

Closed
thomas11 opened this issue Jul 9, 2024 · 2 comments · Fixed by #3748
Closed
Assignees
Labels
3.0 impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone

Comments

@thomas11
Copy link
Contributor

thomas11 commented Jul 9, 2024

When Azure API version 2022-01-01 is the default for a resource in v2, and in v3 the new default is 2024-01-01, then the previous default 2022-01-01 should still be available in v3 as an explicit import. That enables to upgrade without changes, other than import paths.

We had already planned that for v2 but missed.

@thomas11 thomas11 added impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features 3.0 labels Jul 9, 2024
@cleverguy25
Copy link

Added to epic https://github.com/pulumi/home/issues/3552

@pulumi-bot
Copy link
Contributor

This issue has been addressed in PR #3748 and shipped in release v2.76.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0 impact/usability Something that impacts users' ability to use the product easily and intuitively kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants