Skip to content
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

deployment template: fix extraSidecars indentation #770

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zackse
Copy link

@zackse zackse commented Dec 10, 2024

Proposed changes

In the deployment template, the extraSidecars object is indented too far, resulting in malformed YAML.

# test-values.yaml
extraSidecars:
  - name: busy-beaver
    image: busybox
    command: ["sh", "-c"]
    args: ["sleep 999999"]
cd pulumi-kubernetes-operator/deploy/helm/pulumi-operator
helm template . -f test-values.yaml

Error: YAML parse error on pulumi-kubernetes-operator/templates/deployment.yaml: error converting YAML to JSON: yaml: line 34: did not find expected key

This change reduces the indentation to match the manager entry in the containers list.

Notes

  • Ideally this can be included in the 0.8.x release train as 2.x is still unreleased
  • As far as I can tell, this has been an issue since the file was introduced in feat: add helm chart #379
  • Aside, the PR template has a reference to CONTRIBUTING.md, but that file doesn't seem to exist in the repo

The extraSidecars list is indented further than the manager container, so the resulting rendered template is malformed YAML.
Copy link

PR is now waiting for a maintainer to run the acceptance tests. This PR will only perform build and linting.
Note for the maintainer: To run the acceptance tests, please comment /run-acceptance-tests on the PR

Copy link
Contributor

@EronWright EronWright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix!

@EronWright
Copy link
Contributor

I'll take care to merge this PR when we do our next release.

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