This page outlines the annotations supported by Config Connector resources.
Generic annotations can be applied to all Config Connector resources. You can find the list of generic annotations and their descriptions in the following table.
||Can be "none" or "resource". For more details see Managing conflicts with multiple Config Connector resources. Default value is "none".|
Resource-specific annotations configure Config Connector to take additional actions beyond creating or deleting resources.
For example, Cloud Storage doesn't let you delete a
contains objects. Applying the
force-destroy annotation to the bucket and then
deleting the bucket causes Config Connector to delete all of the objects within
the bucket first, then deletes the bucket.
For example, the
force-destroy directive is declared in the following YAML
metadata: annotations: cnrm.cloud.google.com/force-destroy: "true"
Check each Config Connector resource's reference page to learn resource-specific annotations.
Annotations for internal usage
The following annotations are managed by Config Connector. You must never set or edit any of them.
||This annotation is added and managed by Config Connector for resources with mutable but unreadable fields (for example, "password" field in some resource spec).|
||This annotation is added and managed by Config Connector for resources with sensitive fields.|
||This annotation is added and managed by Config Connector for resources with server-side apply enabled .|
||This annotation is added for resources used in KRM blueprints.|