Make it possible to only upgrade providers without updating state

[aucampia]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

We heavily rely on --target/--target-dependents but with Pulumi versions newer than v3.108.1 we are having trouble as it is no longer possible to update a resource if the resource's provider version changed. The error we get when we try to do this is something like:

error: provider urn:pulumi:staging::Kron::pulumi:providers:azure-native::default_2_37_0::667e5587-42b6-46b1-a762-97f7866efe33 for resource urn:pulumi:staging::Kron::pkg:index:AzureComponent$azure-native:authorization:RoleAssignment::herman.schistad@kron.no-READER-subscription has not been registered yet, this is due to a change of providers mixed with --target. Change your program back to the original providers

If it was possible to run an update targetting the current state with new provider versions, then it would make things a bit easier on us.

I think it may be possible to hack something like this together by exporting the state to YAML that looks like YAML input and then changing our runtime to YAML temporarily, but it would be nice to not have to do this.

This is related to:

• --targets can't handle provider versions changing for un-targetted resources #15732
• Pulumi versions after v3.108.1 sometimes crashes/panics when using --target #15704
• pulumi up --target affects providers on non-targeted resources #14254

Affected area/feature

• pulumi up

[justinvp]

Thanks for opening this request, @aucampia, and sorry for the trouble.

@Frassle, any suggestions on how to work around this in the meantime?

[oliparcol]

How about switching to a non default provider for the resources so that the version number is no longer included in the provider urn ?

[Frassle]

How about switching to a non default provider for the resources so that the version number is no longer included in the provider urn ?

The ID would still change and cause the same issue afaik.