From 497efef7c97a01332b197dd68a278269a4b64b67 Mon Sep 17 00:00:00 2001 From: Alexandru Avadanii Date: Fri, 12 Jan 2018 23:18:00 +0100 Subject: [PATCH] [PDF] check-jinja: Replace encrypted str w/ dummy During PDF validation using `check-jinja.sh`, most if not all encrypted strings will fail to decrypt due to missing keys on the build server. The templater will fallback to using raw plaintext, leading to `line too long` yamllint violations. Since we don't care about the actual value of the unencrypted string, replace the encrypted one with a dummy (shorter) string. Change-Id: I0f96db0e055bf84ad43a1df4a0f2bd86cc50fd22 Signed-off-by: Alexandru Avadanii --- config/utils/check-jinja2.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/config/utils/check-jinja2.sh b/config/utils/check-jinja2.sh index f23d389c..c33bef50 100755 --- a/config/utils/check-jinja2.sh +++ b/config/utils/check-jinja2.sh @@ -43,7 +43,9 @@ while IFS= read -r lab_config; do echo 'Result: PASS' ((pdf_inst_pass+=1)) echo -e "\nyamllint -s ${jinja_template%.j2}" - if yamllint -s "${TMPF}"; then ((pdf_yaml_pass+=1)); fi + if yamllint -s <(sed 's|ENC\[PKCS.*\]|opnfv|g' "${TMPF}"); then + ((pdf_yaml_pass+=1)); + fi else echo 'Result: FAIL' RC=1 -- 2.16.6