Custom Resource Options
A bag of optional settings that control a KotlinResource behavior.
Constructors
Functions
Properties
List of aliases for a resource or component resource. If you're changing the name, type, or parent path of a resource or component resource, you can add the old name to the list of aliases for a resource to ensure that existing resources will be migrated to the new name instead of being deleted and replaced with the new named resource.
Set of custom timeouts for create, update, and delete operations on a resource. These timeouts are specified using a duration string such as “5m” (5 minutes), “40s” (40 seconds), or “1d” (1 day). Supported duration units are “ns”, “us” (or “µs”), “ms”, “s”, “m”, and “h” (nanoseconds, microseconds, milliseconds, seconds, minutes, and hours, respectively).
A resource may need to be replaced if an immutable property changes. In these cases, cloud providers do not support updating an existing resource so a new instance will be created and the old one deleted. By default, to minimize downtime, Pulumi creates new instances of resources before deleting old ones.
The dependsOn resource option creates a list of explicit dependencies between resources.
The ignoreChanges resource option specifies a list of properties that Pulumi will ignore when it updates existing resources. Any properties specified in this list that are also specified in the resource's arguments will only be used when creating the resource.
Provides a list of transformations to apply to a resource and all of its children. This option is used to override or modify the inputs to the child resources of a component resource. One example is to use the option to add other resource options (such as ignoreChanges or protect). Another example is to modify an input property (such as adding to tags or changing a property that is not directly configurable).
Marks a resource to be retained. If this option is set then Pulumi will not call through to the resource provider's Delete
method when deleting or replacing the resource during pulumi up
or pulumi destroy
. As a result, the resource will not be deleted from the backing cloud provider, but will be removed from the Pulumi state.