It's useful to know what kind of objects shipper is rendering before
they reach the api server. For debugging issues with YAML
serializing/deserializing, for instance.
For that, you can now run shipperctl chart render --app foobar or
shipperctl chart render --relelase foobar-deadbeef-0, and shipperctl
will print a whole bundle of YAML to stdout, with each object separated
by a ---.
This is currently only useful for applications that already exist, as
you can't manually pass standalone chart spec or values. We'll
eventually support that once we figure out a non-awkard interface for
doing that.
It's useful to know what kind of objects shipper is rendering before they reach the api server. For debugging issues with YAML serializing/deserializing, for instance.
For that, you can now run
shipperctl chart render --app foobar
orshipperctl chart render --relelase foobar-deadbeef-0
, and shipperctl will print a whole bundle of YAML to stdout, with each object separated by a---
.This is currently only useful for applications that already exist, as you can't manually pass standalone chart spec or values. We'll eventually support that once we figure out a non-awkard interface for doing that.