Closed t0yv0 closed 1 year ago
I figured out what's the problem here. There's an implicit parameter in '.upgrade-config.yml':
pulumi-infer-version: true
It's not documented in upgrade-provider --help and there's no way to unset it once it gets implicitly set. It took me some interesting bisect debugging to figure this out.
Once this parameter is set, --target-version is ignored in favor of doing a search on the repo.
This is pretty complicated and unexpected for the user. Consider making some changes so that when the user specifies an explicit version that's what the provider gets upgraded to.
For now I can workaround my scenario by editing .upgrade-config.yml
Sorry about the problem and thanks for investigating. #202 will fix this. It's just waiting on review now.
What happened?
AWS: ff40da2f970359b77452b2ea16daf87ea0d0d1bf upgrade-provider: b0aa77c75695980e4d188e1ea9df7a3e6be4d215
Example
Not having luck updating pulumi-aws, even specifying the version manually.
Output of
pulumi about
N/A
Additional context
N/A
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).