If I had to guess this is likely some kind of automation API bug related to static global state being set in the first run that isn't being cleaned up, and is then causing the second run to fail. You might want to open an issue and see if you can get a small repro together
Not sure it is the same as your case though, but who knows
d
dazzling-salesclerk-51689
05/25/2021, 10:01 AM
@proud-pizza-80589 - no luck on downgrading but thanks.
@bored-oyster-3147 - Yes, agree that it looks like state related issue. opened an issue. thanks.
No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.