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.

Sign up for GitHub

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

Jump to bottom

Restrict charts to work on via argument #8

Closed
fuhbar opened this issue Jun 17, 2017 · 2 comments
Closed

Restrict charts to work on via argument #8

fuhbar opened this issue Jun 17, 2017 · 2 comments

Comments

@fuhbar
Copy link

fuhbar commented Jun 17, 2017

Hi,

just stumbled over this tool and could not image how to live without it! Idea is brilliant as it is simple. Thanks for that. :)

I was just wondering, if there is an argument which limits the list of charts to work on by some kind of expression. Its not always desired to iterate across the whole list of charts. Nevertheless its easily possible to write just a charts.yaml which lists only the desired charts, but this is some kind of cumbersome.

Image something like that: helmfile charts --limit "metrics*" which just works on the charts where the given glob pattern match against.
@roboll
Copy link
Owner

roboll commented Jun 20, 2017

Thanks for the feedback, glad you are making good use of it. 😎

This seems reasonable, I guess for cases where you have a single large helmfile. It could be dangerous in that it could lead to some skew between the charts.yaml and kube, but I guess thats up to the user.

You could also just split out into metrics.yaml, apps.yaml, whatever and helmfile -f metrics.yaml ....

I'd accept a PR for this but I won't have time to implement it myself for a while.

@fuhbar fuhbar mentioned this issue Jun 25, 2017
Closed
@roboll
Copy link
Owner

roboll commented Oct 25, 2017

Closing this due to inactivity, if someone has a strong feeling about this and wants to open a PR I'm open to it.

@roboll roboll closed this as completed Oct 25, 2017
@awwithro awwithro mentioned this issue Jan 25, 2018
Merged
mumoshu pushed a commit that referenced this issue Mar 23, 2018
@awwithro @mumoshu
Allow running helmfile against a subset of releases (#30)
4b08ea9 
This adds `releases[].labels` in which you can set arbitrary number of key-value pairs, so that commands like `helmfile sync --selector key=value` can be used to run the helmfile subcommand against a subnet of declared releases.

`labels` and `selector` are named as such on purpose of being consistent with terminology of Kubernetes and other tools in the K8S ecosystem, including kubectl, stern, helm, and so on.

Resolves #8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roboll @fuhbar