CI, helm-schema-validation.sh: Add -fsS so it returns a non-zero exit code on failure while keeping the output clean (!8339) · Merge requests · Sylva-projects / sylva-core

Closes #4273 (closed)

If the network drops or the URL returns a 404, curl -s will still exit with status code 0, masking the failure and leaving an empty file.

This causes jsonschema to crash.

This MR will add -f (--fail) and will successfully catch HTTP errors (like 404 Not Found or 500 Internal Server Error).

With this change fail will be fast and exit with an error code and no checking against empty file.

Also adding -S (or --show-error) flag tells curl to print a human readable error message if the download fails, even when it is running in silent mode (-s)

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

CI, helm-schema-validation.sh: Add -fsS so it returns a non-zero exit code on failure while keeping the output clean

CI configuration

Global config for deployment pipelines

Merge request reports