airship/airshipctl
Code Issues Proposed changes

Fixed docs validation build

Browse Source 
Phases should be ordered when rendering to prevent error like:
'... no matches for kind "Cluster" ...'

Change-Id: I830c36b5959ae3970b261f96ff6d23bf467f5ff6
This commit is contained in:
Stanislav Egorov 2020-07-09 15:02:25 -07:00 committed by Stas Egorov
parent 1cafd674df
commit 9fddcbdf3b
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
tools/document/validate_site_docs.sh
View File

@ -109,12 +109,14 @@ for cluster in ephemeral target; do
sed -i "s/${CONTEXT}/${CONTEXT}_${cluster}/" ${AIRSHIPKUBECONFIG}
generate_airshipconf ${cluster}
for phase in $(ls manifests/site/${SITE}/${cluster}| grep -v "\.yaml$"); do
${ACTL} cluster init
phases="bootstrap initinfra "
ignore=$(for i in $phases; do echo "-I $i "; done)
phases+=$(ls $ignore manifests/site/${SITE}/${cluster}| grep -v "\.yaml$")
for phase in $phases; do
echo -e "\n*** Rendering ${cluster}/${phase}"
# step 1: actually apply all crds in the phase
# TODO: will need to loop through phases in order, eventually
# e.g., load CRDs from initinfra first, so they're present when validating later phases
${ACTL} phase render ${phase} -k CustomResourceDefinition > ${TMP}/crds.yaml
if [ -s ${TMP}/crds.yaml ]; then
${KUBECTL} --context ${CONTEXT} --kubeconfig ${KUBECONFIG} apply -f ${TMP}/crds.yaml