2f5402ae80
Command phase run will be used instead, so phase apply became no longer needed. Change-Id: I8bdbd6bcad7efbb03632978d8952700fc39d55ba Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
32 lines
876 B
Markdown
32 lines
876 B
Markdown
## airshipctl phase
|
|
|
|
Manage phases
|
|
|
|
### Synopsis
|
|
|
|
This command provides capabilities for interacting with phases,
|
|
such as getting list and applying specific one.
|
|
|
|
|
|
### Options
|
|
|
|
```
|
|
-h, --help help for phase
|
|
```
|
|
|
|
### Options inherited from parent commands
|
|
|
|
```
|
|
--airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config")
|
|
--debug enable verbose output
|
|
--kubeconfig string Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig")
|
|
```
|
|
|
|
### SEE ALSO
|
|
|
|
* [airshipctl](airshipctl.md) - A unified entrypoint to various airship components
|
|
* [airshipctl phase plan](airshipctl_phase_plan.md) - List phases
|
|
* [airshipctl phase render](airshipctl_phase_render.md) - Render phase documents from model
|
|
* [airshipctl phase run](airshipctl_phase_run.md) - Run phase
|
|
|