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

Keep the top-level resource stable within a major version #512

Closed
mikhailshilkov opened this issue Feb 12, 2021 · 0 comments · Fixed by #634
Closed

Keep the top-level resource stable within a major version #512

mikhailshilkov opened this issue Feb 12, 2021 · 0 comments · Fixed by #634
Assignees
Labels
kind/enhancement Improvements or new features
Milestone

Comments

@mikhailshilkov
Copy link
Member

Design and implement the mechanism to keep the top-level resources stable within a major version.

According to our plan in pulumi/pulumi-azure-nextgen#169 (comment):

At 1.0, for a given resource, we will likely pick an API version that is the latest. If a later version is published by Microsoft and it contains breaking changes, we will NOT introduce this version to the top-level resource. It will be available under a versioned namespace only.

One obvious way is to stop updating provider_list.json but let's spend some time considering pros/cons and other options.

@leezen leezen added this to the 0.53 milestone Mar 2, 2021
@mikhailshilkov mikhailshilkov added the kind/enhancement Improvements or new features label Mar 3, 2021
@mikhailshilkov mikhailshilkov self-assigned this Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants