fancy-pharmacist-39201
05/24/2023, 7:01 AMpulumi up
because Pulumi incorrectly thinks it needs to recreate all my resources. I tried pulumi stack export
but I don't know with what to replace the token
and apiToken
input and output strings in the providers: when I replace them with the appropriate encrypted values from my Pulumi.<stack>.yaml
file, I get "could not deserialize deployment: invalid character 'Y' after top-level value" on the import, so presumably they need to be somehow different between the state file and the stack config file. I also tried pulumi refresh --target <urn of the provider>
, but that appears to have been a no-op; and pulumi up --target <urn of the provider>
said there was no resource with that URN. How can I tell Pulumi to use the correct credentials in a refresh operation?pulumi state delete
on the provider URNs, in the hope that I could then recreate it from scratch, but that's forbidden because other state depends on it.)echoing-dinner-19531
05/24/2023, 7:27 AMpulumi up --target=provider_urn
to get just the provider state updated to the latest tokens, and then do a refresh to get everything else updated.up
saying there was no resource by that URN might mean you just got the URN copied wrong, or if these are default providers maybe they're not getting picked up by --target, which esh we should look into.fancy-pharmacist-39201
05/24/2023, 7:31 AMpulumi stack export
output - just tried again with the same "no resource with that URN" resultechoing-dinner-19531
05/24/2023, 7:57 AMlittle-cartoon-10569
05/24/2023, 8:25 PMfancy-pharmacist-39201
05/24/2023, 10:21 PMpulumi up
worked, I just didn't want to do it before a pulumi refresh
because my state was out of sync