
Plan validation: 1. Each phase must be defined within phase document bundle. 2. Each phase does not return error for Validate method Phase validation: 1. Document bundle associated with the phase can be rendered without an error. 2. Associated executor must not return an error. Relates-to: #330 Change-Id: I08c5e8e42570f2cafdced5a02481b033414ffae0
39 lines
656 B
YAML
39 lines
656 B
YAML
apiVersion: airshipit.org/v1alpha1
|
|
kind: PhasePlan
|
|
metadata:
|
|
name: phasePlan
|
|
phases:
|
|
- name: isogen
|
|
- name: remotedirect
|
|
- name: initinfra
|
|
- name: some_phase
|
|
- name: capi_init
|
|
---
|
|
apiVersion: airshipit.org/v1alpha1
|
|
kind: PhasePlan
|
|
metadata:
|
|
name: init
|
|
phases:
|
|
- name: capi_init
|
|
---
|
|
apiVersion: airshipit.org/v1alpha1
|
|
kind: PhasePlan
|
|
metadata:
|
|
name: some_plan
|
|
phases:
|
|
- name: some_phase
|
|
---
|
|
apiVersion: airshipit.org/v1alpha1
|
|
kind: PhasePlan
|
|
metadata:
|
|
name: plan_invalid_phase
|
|
phases:
|
|
- name: no_entry_point
|
|
---
|
|
apiVersion: airshipit.org/v1alpha1
|
|
kind: PhasePlan
|
|
metadata:
|
|
name: phase_not_exist
|
|
phases:
|
|
- name: non_existent_name
|