-
Notifications
You must be signed in to change notification settings - Fork 51
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
Upgrading from v4 to v5 causes storage accounts to be recreated #1593
Labels
kind/bug
Some behavior is incorrect or out of spec
Comments
barclayadam
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Jan 5, 2024
barclayadam
changed the title
UPgrading from v4 to v5 causes storage accounts to be recreated
Upgrading from v4 to v5 causes storage accounts to be recreated
Jan 5, 2024
Hi @barclayadam. Thanks for reporting this issue. This looks like a bug on our end. You might be able to work-around the bug by replacing |
Hi @iwahbe. Do you mean by making a change in the state beforehand? |
Yes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Upgrading from
4.37.0
to^5.60.0
has caused all storage accounts to require a replacement. I can see nothing that has changed in the output. The only diff in source is replacingallowPublicAccess
withallowNestedItemsToBePublic
as required.The complete diff output in Pulumi web app shows no changes:
I'm using the Automation API and have checked all events, and none of them contain any useful information on what it believes has changes
Example
Output of
pulumi about
CLI
Version 3.84.0
Go Version go1.21.1
Go Compiler gc
Plugins
NAME VERSION
azure 5.60.0
azure-native 2.24.0
azuread 5.46.0
cloudflare 5.0.0
docker 3.0.0
kubernetes 3.30.2
newrelic 5.10.0
nodejs unknown
random 4.0.0
tls 4.0.0
Host
OS Microsoft Windows 11 Pro
Version 10.0.22000 Build 22000
Arch x86_64
Additional context
No response
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).
The text was updated successfully, but these errors were encountered: