-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add apply_only argument. Add force_conflicts option. #148
Conversation
@kahirokunn what about also being able to define the field manager name? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@gavinbunney when do you think this will get released to terraform registry? |
@@ -42,6 +42,8 @@ YAML | |||
* `sensitive_fields` - Optional. List of fields (dot-syntax) which are sensitive and should be obfuscated in output. Defaults to `["data"]` for Secrets. | |||
* `force_new` - Optional. Forces delete & create of resources if the `yaml_body` changes. Default `false`. | |||
* `server_side_apply` - Optional. Allow using server-side-apply method. Default `false`. | |||
* `force_conflicts` - Optional. Allow using force_conflicts. Default `false`. | |||
* `apply_only` - Optional. It does not delete resource in any case Default `false`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/ Default/. Default/
https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html
Some cloud providers have resources such as
aws-auth
configmap that can be applied but never deleted permanently.It would be smart to handle such cases as well.