pulumi up fails on with 2.9.0 but works in 2.8.0 due to breaking CustomDomain.verification field name change #144
Labels
impact/usability
Something that impacts users' ability to use the product easily and intuitively
kind/bug
Some behavior is incorrect or out of spec
resolution/wont-fix
This issue won't be fixed
What happened?
#141 introduced a breaking change where the
verification
field of the CustomDomain resource was renamed toverifications
. Our Pulumi program uses that field to create a Route53 record, but after upgrading it crashes with the following error:Here's the relevant piece of code for the above:
The resource in the state file looks like this:
Steps to reproduce
I unfortunately don't have time to create a stand-alone minimal reproduce case to link to right now, but here's the general outline:
verification
field.pulumi preview
. It should throw an error aboutverification
not being a valid field.verification
toverifications
in your code and try again.verifications
.Trying to manually edit the state file to change the name of the field there to
verifications
doesn't work either.Expected Behavior
The
verification
field should exist and have the same schema as it did in version 2.8.0. The upstream Terraform provider 0.30.2 does not contain this change.Actual Behavior
Upgrading to 2.9.0 causes the issue described above instead of succeeding as it does in 2.8.0. Downgrading to 2.8.0 restores the functionality.
Versions used
Additional context
We're unable to deploy our stack that uses
pulumi-auth0
on version 2.9.0 because of this issue: we're stuck with either the code error about the invalid field name, or the invalid state, which means we cannot use this version at all. We have to stay on the older version in order to keep the team moving forward.Since this is breaking change, I would have expected a major version bump and a migration guide on how to update our user-land code to the new changes.
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: