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
When the image-automation-controller updates an image on a yaml file, it seems to have the default behaviour to remove any blank lines in the file.
In most manifests this may be fine, but the image-automation-controller is able to update non-manifest yaml files, e.g. .gitlab-ci.yml, docker-compose.yml, etc. For these files it is fairly common to have blank lines between structured blocks.
Is it currently possible, or would it be possible to have the image-automation-controller preserve these blank lines (and any general structure in the YAML file), so that it effectively only edits the lines that are intended to be edited?
The text was updated successfully, but these errors were encountered:
We're pretty much depending on the upstream kyaml lib for this functionality and that doesn't have a way to preserve blank lines. I'd be more than happy if you would be able to raise a ticket with the kustomize project in this matter.
Thanks @makkes for the reply. I would like to raise the ticket on kustomize project. Is there any additional info, I can add to the ticket for when the image-automation-controller applies its changes?
When the image-automation-controller updates an image on a yaml file, it seems to have the default behaviour to remove any blank lines in the file.
In most manifests this may be fine, but the image-automation-controller is able to update non-manifest yaml files, e.g. .gitlab-ci.yml, docker-compose.yml, etc. For these files it is fairly common to have blank lines between structured blocks.
Is it currently possible, or would it be possible to have the image-automation-controller preserve these blank lines (and any general structure in the YAML file), so that it effectively only edits the lines that are intended to be edited?
The text was updated successfully, but these errors were encountered: