This message was deleted.

sparse-intern-71089

12/15/2020, 1:02 AM

This message was deleted.

little-cartoon-10569

12/15/2020, 2:20 AM

You could

pulumi state delete urn:pulumi:dev1::ucboitlake::aws:redshift/snapshotScheduleAssociation:SnapshotScheduleAssociation::redshift-snapshot-schedule-association

🙌 1

✅ 1

mysterious-oyster-86659

12/15/2020, 3:56 AM

wow that worked, so clearly I'm not understanding something. thank you for your input @little-cartoon-10569! I thought that

refresh

was specifically made for accommodating the changing so-called "state" of a given stack when making alteration via console or CLI what am I missing or getting wrong here?

little-cartoon-10569

12/15/2020, 3:59 AM

Pulumi uses the state to determine what resources to "look up" in your cloud provider. If the information in the state that enables the look-up is wrong (e.g. in this case, it points to something that doesn't exist), then Pulumi can't use that information to update its own state.

little-cartoon-10569

12/15/2020, 4:00 AM

Essentially: Pulumi can detect change in known resources, but it can't detect the manual creation, deletion, or replacement of a resource if the change has materially affected the resource's ARN (or whatever is used to find the resource).

👍 1

mysterious-oyster-86659

12/15/2020, 3:04 PM

@little-cartoon-10569 I think that makes sense, but I need to test more to really get it. Thanks again for the help!

👍 1

Open in Slack

Previous Next

Pulumi Community

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.