From 53cf713a08c9985b3eeb5889be25cfe85c671310 Mon Sep 17 00:00:00 2001 From: Sreejith Punnapuzha Date: Thu, 9 Jul 2020 09:03:37 -0500 Subject: [PATCH] Generate document CRD to different files This commit adds generating CRD into different files for each phase Change-Id: I574b27d737f946415e64eaf5b1d5bf962d6c2cc1 Signed-off-by: Sreejith Punnapuzha --- tools/document/validate_site_docs.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/document/validate_site_docs.sh b/tools/document/validate_site_docs.sh index 3bb8ae728..c99c8784c 100755 --- a/tools/document/validate_site_docs.sh +++ b/tools/document/validate_site_docs.sh @@ -121,9 +121,9 @@ for cluster in ephemeral target; do # 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 + ${ACTL} phase render ${phase} -k CustomResourceDefinition > ${TMP}/${phase}-crds.yaml + if [ -s ${TMP}/${phase}-crds.yaml ]; then + ${KUBECTL} --context ${CONTEXT} --kubeconfig ${KUBECONFIG} apply -f ${TMP}/${phase}-crds.yaml fi # step 2: dry-run the entire phase