-
Notifications
You must be signed in to change notification settings - Fork 16
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
Kargo Render should ignore contents of configmap when rendering #278
Comments
@jimil749 I assume you don't mean that the contents of a cm shouldn't be rendered. I assume you mean we should take greater care here to only split on kargo-render/internal/manifests/manifests.go Lines 29 to 56 in 6de5d79
If that was your meaning, I agree. |
@krancour exactly. Contents of a cm should be rendered but greater care needs to take to split on |
This seems to be happening a quite a few charts. |
I am trying to render manifest for apache airflow (by using kustomize + upstream helm charts). It includes a configmap manifest which looks like following:
This breaks the render with the following error:
level=fatal msg="error writing manifests for app \"airflow\" to \"/tmp/2142585927/repo/airflow\": resource is missing kind field"
This is because of "---" in the configmap data. Render splits the above manifest into 2 parts (since it uses "---" as the separator) which cause the render to fail.
Render would work fine if it is possible to just ignore the contents of cm.
The text was updated successfully, but these errors were encountered: