This message was deleted.
# generals
sparse-intern-71089
03/08/2021, 8:46 PMThis message was deleted.
l
little-cartoon-10569
03/08/2021, 9:10 PMYou could search the changelog? https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md
b
bored-oyster-3147
03/08/2021, 9:11 PMDid you encounter this because your Automation API package needed a specific version of the CLI? If so I believe there is a currently open issue about making those error messages tell you what version of the CLI you need. https://github.com/pulumi/pulumi/issues/6419
l
loud-battery-37784
03/09/2021, 2:05 PMI encountered this because I was looking through the docs and found a command that failed on the CLI we have installed on our development platform. I was wanting to request our Pulumi CLI be upgraded to use the new command but needed to know what the minimum version requirement for that is.
l
little-cartoon-10569
03/09/2021, 8:15 PMI infer that you're looking to upgrade to the oldest version that you can get away with. Would it not be more future-proof to upgrade to the newest version you can?
l
loud-battery-37784
03/09/2021, 8:48 PMFor sure the newest would be ideal, however, as an IC I don’t always have say in what version of CLI tooling we use.
To circle back, I just searched the changelog and it doesn’t say when
change-secrets-providerl
little-cartoon-10569
03/09/2021, 8:50 PMI see this:
2.8.0 (2020-08-04)
Add missing MapMap and ArrayArray types to Go SDK #5092
Switch os/user package with luser drop in replacement #5065
Update pip/setuptools/wheel in virtual environment before installing dependencies #5042
Add ability to change a secrets provider for the current stack #5031
little-cartoon-10569
03/09/2021, 8:53 PMThough I see that there have been a few enhancements and bugfixes to that feature since then: 2.19.0, 2.15.1, 2.15.0. You may need some of those?
little-cartoon-10569
03/09/2021, 8:55 PMThat said, I think this particular feature wouldn't require the entire org to change version. You could use a later version to make the change, which would re-write your yaml files etc., Older versions could then use the newer files. So you might not need to wait for the entire org to update.
l
loud-battery-37784
03/09/2021, 10:29 PMAh, nice find. I searched for the actual command. We utilize a custom container to run all our CICD processes in with all our CLI tooling and security built into it. So tooling needs to move as one. Pros and cons to that concept. Either way. Just wanted to say it might make sense to put which version new CLI commands are introduced into the docs on the site somewhere.
l
little-cartoon-10569
03/09/2021, 10:31 PMYep. Feature request I guess? A standard convention for comments that get into the changelog?