Skip to content

fix(deployment-init-container): Update _deployment.yaml to support 3d tools like Vals #455

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

Merged
merged 2 commits into from
Apr 23, 2024

Conversation

nofearOnline
Copy link
Contributor

What

Fixing the init container in the runner deployment template. Removing redundent space that cause issues when using 3d tools like Vals (helmfile/vals)

Why

There is an issue with your helm chart using 3d tools like Vals (helmfile/vals). You have an extra space which cause "mapping values are not allowed in this context" error in 3d tools reading the template result of the cf-runner helm chart.

This change fixes this bug without changing anything else.

Notes

We at Honeybook are one of your customers and this issue is a blocker to several of our tasks.

POC:
image

There is an issue using 3d tools like Vals (helmfile/vals). You have an extra space which cause "mapping values are not allowed in this context" error in Vals
@mikhail-klimko mikhail-klimko changed the title Fix(deployment-init-container): Update _deployment.yaml to support 3d tools like Vals fix(deployment-init-container): Update _deployment.yaml to support 3d tools like Vals Apr 23, 2024
@mikhail-klimko mikhail-klimko merged commit a4dfdb1 into codefresh-io:release-1.0 Apr 23, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants