Allow Pulumi.yaml to set default plugin version #15714
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changelog[uncommitted] (2024-03-17)Features
|
Frassle
force-pushed
the
fraser/pluginVersionDefault
branch
2 times, most recently
from
0f84a99
to
35d4408
Compare
Frassle
force-pushed
the
fraser/pluginVersionDefault
branch
from
35d4408
to
173ef2d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This allows the Pulumi.yaml to specify the default version for a provider plugin. This is mostly of use in YAML where we don't have a generated SDK to fill in 'version' for every resource request for us.
An obvious follow up to this is to also use this to set the default plugin download url.
Note that YAML does already have a way to support this, by declaring a provider resource and tagging it as "default". This just makes that logic more first-class supported by the engine given that this providers section is probably going to become more common to use with local SDK generation, parameterised providers, and possibly plugin version lock files.
Checklist
make tidyto update any new dependenciesmake lintto verify my code passes the lint checkgofumptmake changelogand committed thechangelog/pending/<file>documenting my change