Add list-changed command #98
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
unguiculus
force-pushed
the
list-changed
branch
from
8e9da21
to
db52fef
Compare
Allows to identify chart changes before actually running lint or install commands. This can be useful in the following cases: * In a CI setup where kind clusters are spun up on the fly, this makes it possible to decide whether a cluster is necessary at all. A PR may only contain changes that are not relevant to any charts. * By knowing upfront which charts have changed, it is possible to load a per-chart CI configuration which would allows us to determine the number of nodes needed in a kind cluster. For most charts, one node is enough, but in certain scenarios, especially for StatefulSets, we may want to test with pod anti-affinity where replicas have to be spread across multiple nodes. Signed-off-by: Reinhard Nägele <unguiculus@gmail.com>
unguiculus
force-pushed
the
list-changed
branch
from
db52fef
to
ab5b46c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows to identify chart changes before actually running
lint or install commands. This can be useful in the following
cases:
this makes it possible to decide whether a cluster is necessary
at all. A PR may only contain changes that are not relevant
to any charts.
possible to load a per-chart CI configuration which would
allows us to determine the number of nodes needed in a kind
cluster. For most charts, one node is enough, but in certain
scenarios, especially for StatefulSets, we may want to test
with pod anti-affinity where replicas have to be spread across
multiple nodes.
Signed-off-by: Reinhard Nägele unguiculus@gmail.com