airship/airshipctl
Code Issues Proposed changes
airshipctl/docs/source/cli/airshipctl_phase_render.md
Kostiantyn Kalynovskyi 6807547ab2 Add ability to render different document sets 
Now we would be able to render phase bundle, executor bundle
and config bundle. Config bundle will contain documents such as
phases and executors.

Relates-To: #459
Closes: #459

Change-Id: Ia6b9196dfb3d8fb3264fef676c975ccc32883fee
2021-02-04 17:40:35 +00:00

1.6 KiB
Raw Blame History

airshipctl phase render

Render phase documents from model

Synopsis

Render phase documents from model

airshipctl phase render PHASE_NAME [flags]

Examples


# Get all 'initinfra' phase documents containing labels "app=helm" and
# "service=tiller"
airshipctl phase render initinfra -l app=helm,service=tiller

# Get all phase documents containing labels "app=helm" and "service=tiller"
# and kind 'Deployment'
airshipctl phase render initinfra -l app=helm,service=tiller -k Deployment

# Get all documents from config bundle
airshipctl phase render --source config

# Get all documents executor rendered documents for a phase
airshipctl phase render initinfra --source executor

Options

  -a, --annotation string   filter documents by Annotations
  -g, --apiversion string   filter documents by API version
  -h, --help                help for render
  -k, --kind string         filter documents by Kinds
  -l, --label string        filter documents by Labels
  -s, --source string       phase: phase entrypoint will be rendered by kustomize, if entrypoint is not specified error will be returned
                            executor: rendering will be performed by executor if the phase
                            config: this will render bundle containing phase and executor documents (default "phase")

Options inherited from parent commands

      --airshipconf string   Path to file for airshipctl configuration. (default "$HOME/.airship/config")
      --debug                enable verbose output

SEE ALSO