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

[BUG][opensearch] helm lint fails if using extraObjects #606

Closed
cyanidium opened this issue Oct 20, 2024 · 1 comment · Fixed by #607
Closed

[BUG][opensearch] helm lint fails if using extraObjects #606

cyanidium opened this issue Oct 20, 2024 · 1 comment · Fixed by #607
Labels
bug Something isn't working

Comments

@cyanidium
Copy link
Contributor

Describe the bug
When running helm lint and creating any extra objects using the extraObjects value, helm lint fails with:

[ERROR] templates/extraManifests.yaml: unable to parse YAML: invalid Yaml document separator: apiVersion: apps/v1

To Reproduce
Steps to reproduce the behavior:

  1. Create a values.yaml with extraObjects defined
  2. Run helm list -f values.yaml charts/opensearch from the repo top level
  3. See error

Expected behavior
There should be no errors during linting.

Chart Name
opensearch

Screenshots
If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

  • Helm Version: v3.16.2
  • Kubernetes Version: N/A

Additional context
This is a known issue with helm and only affects linting, not the applied templates:
helm/helm#10149

@cyanidium cyanidium added bug Something isn't working untriaged Issues that have not yet been triaged labels Oct 20, 2024
@prudhvigodithi
Copy link
Collaborator

[Triage]
Thanks @cyanidium we can get the PR's reviewed and merged for this issue.
@peterzhuamazon

@prudhvigodithi prudhvigodithi removed the untriaged Issues that have not yet been triaged label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

2 participants