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

docs: warn users on ingoring tgz files in helmignore #1594

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

Conversation

banjoh
Copy link

@banjoh banjoh commented Jun 17, 2024

Users may find themselves adding *.tgz in .helmignore. Doing so will ignore all chart dependencies from being packaged using helm package. The command will fail in mysterious ways as can be seen in helm/helm#12992.

Since dependencies are usually tgz files, we need to warn users of this behaviour.

- The '**' syntax is not supported.
- The globbing library is Go's 'filepath.Match', not fnmatch(3)
- Trailing spaces are always ignored (there is no supported escape sequence)
- There is no support for '\!' as a special leading sequence.
- It does not exclude itself by default, you have to add an explicit entry for `.helmignore`

#### Pitfalls to avoid
- Do not add `*.tgz` to your list of ignore rules because `helm package` will ignore dependency archives from being packaged in your chart. Instead, narrow down your glob filter or specify exact file names in your rule that does not conflict with any dependency packages
Copy link
Contributor

Choose a reason for hiding this comment

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

Did we consider having the package functionality ignore .helmignore rules for dependency archives? Not against documenting this behavior in the interim. But the behavior seems wrong / should be fixed.

Copy link
Contributor

Choose a reason for hiding this comment

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

(put the above comment on the issue)

@karenhchu karenhchu added the docs label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants