This message was deleted.

and I get this error:

Pulumi is only declarative. You cannot change things: you can only declare what they must look like. If you want to update a resource, you must define that entire resource. Since you want to continue to manage that resource outside of Pulumi, you cannot use Pulumi to update it. You can update it in a Pulumi program though, using the normal SDK of whatever provider (AWS, Azure, ...) the resource is in.

so a dynamic provider would be the only interoperable choice in this case? https://www.pulumi.com/docs/concepts/resources/dynamic-providers/ never understood the

pulumi import

workflow, how would that differ?

No. You could manage the resource in Pulumi. Or you could update the resource via its normal SDK. You should almost certainly not try to get Pulumi to update an unmanaged resource.

gotcha, I missed the "normal" in your previous comment, and took it to mean "use the sdk in pulumi" if, for whatever reason, the normal sdk was used to update state outside pulumi, would a

pulumi refresh

be helpful here to resolve drift?

No. Since you're using the SDK directly, that bit of code is imperative, not declarative. You can use the Pulumi get functions where needed, and they also aren't affected by

pulumi refresh

.