You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some cases where there are cloud resources that are scoped to an account - like ServiceLinkedRoles in AWS or Project Services in GCP. Individual deployments will frequently want to ensure the resource exists - but do not want to manage it long term. For example:
If it exists, read it in so it can be referenced
If it does not exist, create it
When the Pulumi resource is deleted - don't remove from the cloud provider
Today, this can't quite be expressed in Pulumi. In principle it would be possible to provide a ResourceOption which would allow expressing this.
This sounds like it would be useful during the Dev process for me at the moment.
My scenario is that I'm testing deploying/destroying stacks multiple times to trial things. My DB server can take anywhere between 10-45 minutes to destroy or provision, so would be great to have this resource option to use during the development phase (or boolean switchable based on config).
Just another potential use case to justify this ;-)
There are some cases where there are cloud resources that are scoped to an account - like
ServiceLinkedRoles
in AWS or Project Services in GCP. Individual deployments will frequently want to ensure the resource exists - but do not want to manage it long term. For example:Today, this can't quite be expressed in Pulumi. In principle it would be possible to provide a
ResourceOption
which would allow expressing this.Related issues: #3388
Design
Implementation Plan
TODO
Announce
The text was updated successfully, but these errors were encountered: