-
Notifications
You must be signed in to change notification settings - Fork 153
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
Enable to ignore manifests' fields from drift detection #4190
Comments
How about definining a new annotation
|
Thanks for the idea, but we think that this feature should be portable to other application kinds which pipecd currently supports, so maybe it's better to make this configuration a part of the pipecd application configuration (the |
It could be more complicated when you specify fields out of the resource. You have to specify the resource name, kind and apiVersion since you can have several resources on one deployment. |
TODO
I don't think terraform's drift detection is necessary for this issue because it doesn't detect it in the manifest diff, so I won't support it for now. |
ECS and Lambda have not yet implemented drift detection, so I will separate them into separate Issues. |
By operating Kubernetes' ignoreManifests, and if it looks OK, I will implement CloudRun's. |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. Feel free to reopen if still applicable. |
What would you like to be added:
Why is this needed:
Some autogenerated fields in k8s manifests changed on each rerun, thus users want to ignore them from the drift detection feature. Would be best if we can make it available via application config.
The text was updated successfully, but these errors were encountered: