helmfile

Commit Graph

Author	SHA1	Message	Date
Alex Withrow	4b08ea9292	Allow running helmfile against a subset of releases (#30 ) 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	2018-03-24 01:05:19 +09:00
bob	76dcc6b182	[state] - Fix issue where spec[].Namespace were ignored	2018-03-05 11:05:58 +01:00
KUOKA Yusuke	0fc74ea771	Fix terminology (#35 ) In a backward compatible manner, so that (I believe) we could move the discussion made in #25 forward. Fixes #25	2018-03-03 00:14:43 +09:00

Author

SHA1

Message

Date

Alex Withrow

4b08ea9292

Allow running helmfile against a subset of releases (#30 )

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

2018-03-24 01:05:19 +09:00

bob

76dcc6b182

[state] - Fix issue where spec[].Namespace were ignored

2018-03-05 11:05:58 +01:00

KUOKA Yusuke

0fc74ea771

Fix terminology (#35 )

In a backward compatible manner, so that (I believe) we could move the discussion made in #25 forward.

Fixes #25

2018-03-03 00:14:43 +09:00

3 Commits