-
Notifications
You must be signed in to change notification settings - Fork 8
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
Upgrade from 4.x to 5.x causes Unknown kind bool error on applications #1338
Labels
Comments
gpduck
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Sep 18, 2024
Thank you for reporting this, @gpduck. I can reproduce it, even when upgrading to v5.0.x first.
|
Hi @gpduck, I believe this issue is already fixed in the latest v5.53.4 of pulumi-azuread. You missed by just one patch version. Your example fails for me as described on 5.53.3 but succeeds on 5.53.4. |
6 tasks
Yes it does appear to be fixed in 5.53.4. Thanks for looking in to it and getting the issue fixed! |
pulumi-bot
added
needs-triage
Needs attention from the triage team
and removed
awaiting-feedback
Blocked on input from the author
labels
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe what happened
'application' resources cause pulumi to crash when upgrading from the 4.x to 5.x @pulumi/azuread provider. There are several properties in state that changed types and the provider is not correctly migrating state. This does not happen in the corresponding terraform provider.
Sample program
terraform going from 1.6.0 to 2.53.0 correctly migrates the state and does not produce an error
Log output
No response
Affected Resource(s)
application
Output of
pulumi about
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: