mirror of https://github.com/pulumi/pulumi.git
4bbe365f15
In many cases there is no need to delete resources if the container resource is going to be deleted as well. A few examples: * Database object (roles, tables) when database is being deleted * Cloud IAM bindings when user itself is being deleted This helps with: * Speeding the deletion process * Removing unnecessary calls to providers * Avoiding failed deletions when the pulumi user running the plan has access to the container resource but not the contained ones To avoid deleting contained resources, set the `DeletedWith` resource option to the container resource. TODO: Should we support DeletedWith with PendingDeletes? Special case might be when the contained resource is marked as pending deletion but we now want to delete the container resource, so ultimately there is no need to delete the contained anymore |
||
|---|---|---|
| .. | ||
| alias_grpc_pb.js | ||
| alias_pb.js | ||
| analyzer_grpc_pb.js | ||
| analyzer_pb.js | ||
| engine_grpc_pb.js | ||
| engine_pb.js | ||
| errors_grpc_pb.js | ||
| errors_pb.js | ||
| language_grpc_pb.js | ||
| language_pb.js | ||
| plugin_grpc_pb.js | ||
| plugin_pb.js | ||
| provider_grpc_pb.js | ||
| provider_pb.js | ||
| resource_grpc_pb.js | ||
| resource_pb.js | ||
| status_grpc_pb.js | ||
| status_pb.js | ||