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
ResourceOptions are often important for controlling how resources are deployed with Pulumi. today, charts and yaml files can be deployed with Pulumi, and a custom ResourceOptions can be passed into all resources. However, it is not possible to provide specific ResourceOptions for individual resources or groups of resources. For example, it is not possible to add additionalSecretOutputs to fields which should be marked secret, or protect to resources which should not be allowed to be deleted.
We should augment transformations to allow users to add/change ResourceOptions for individual resources.
* Allow customizing ResourceOptions in transformations
Adds the ability for transformations to see the current ResourceOptions and modify it if desired on an per-resource basis.
Fixes#574.
* Add CHANGELOG
* Add Python support
* Update CHANGELOG
ResourceOptions are often important for controlling how resources are deployed with Pulumi. today, charts and yaml files can be deployed with Pulumi, and a custom ResourceOptions can be passed into all resources. However, it is not possible to provide specific ResourceOptions for individual resources or groups of resources. For example, it is not possible to add
additionalSecretOutputs
to fields which should be marked secret, orprotect
to resources which should not be allowed to be deleted.We should augment
transformations
to allow users to add/changeResourceOptions
for individual resources.See also #546 (comment).
The text was updated successfully, but these errors were encountered: