Add support for specifying key/value pairs on the command line, instead
of only in a YAML file.
This currently accepts either command line pairs or a YAML file, but
does not support combining the two.
Closes#944
This stops a repeat deletion from sending requests all the way to
Kubernetes, and gives a clear error message when a deletion is requested
on an already deleted resource.
Relates to #972
```
./scripts/coverage.sh 37.25s user 4.15s system 144% cpu 28.615 total
```
```
./scripts/coverage.sh 47.96s user 6.77s system 567% cpu 9.647 total
```
This makes the template system less tolerant in the name of detecting
YAML parse errors before things are sent to Kubernetes. It returns a
more detailed error message when a template creates a manifest which is
not valid YAML.
Closes#957
This fixes a bug in which passed-in values files were not correctly
merged into the chart's default values YAML data. I believe it also
fixes some other prioritization bugs in values merging.
The existing unit test was wrong (see TestCoalesceValues). It is
fixed now. Also added more tests to simulate issue #971.
In the course of writing this, I removed some vestigial code as
mentioned in #920.
Closes#971Closes#920
The README reflected an earlier stage of project development. This
update gives more useful "Why Helm?" documentation at the top, and
updates several of the instructions to be more reflective of current
status.
This includes a substantial bit of unit test improvements. Also, in
order to allow us to tests command line args (which translate to
helm.Option objects), I had to add a new interface to pkg/helm.
Template paths were relative to the chart that contained them, which
meant that all templates were named 'template/SOMETHING'. This made it
trivially easy to hit namespace collisions as in #933.
Template path names are essentially opaque strings so this patch simply
changes them to be qualified by parent chart.