Update devops/azure/chart/templates/deployment.yaml,...

Update devops/azure/chart/templates/deployment.yaml, devops/azure/chart/values.yaml, devops/azure/chart/helm-config.yaml files
2 jobs for !43 with add_node_selector in 21 seconds (queued for 4 seconds)
latest detached
Status Name Job ID Coverage
failed deprecated-pipeline-include #491847
allowed to fail


failed trigger-trusted-tests #491848


Name Stage Failure
trigger-trusted-tests Review
needs to launch a protected pipeline, which by convention is prefixed with 'trusted-'. Only maintainers
can create protected branches. If you are not a maintainer, please ask one to create a trusted branch for
you. They will need to inspect your branch for proper handling of secret variables before applying the trusted label.
If you are a maintainer, you need to push a branch named 'trusted-add_node_selector', then re-run this pipeline.
If all else fails / something weird is going on, the logic in this script is maintained by:
David Diederich, @divido, d.diederich@opengroup.org
Cleaning up file based variables
ERROR: Job failed: exit code 1
deprecated-pipeline-include .Pre
Reinitialized existing Git repository in /builds/osdu/platform/security-and-compliance/entitlements-azure/.git/
Checking out dbdd1f30 as refs/merge-requests/43/head...

Skipping Git submodules setup
Executing "step_script" stage of the job script
The FOSSA scanner now supports different build environments, which should be specified directly. Consider using fossa-maven.yml instead.
$ /bin/false
ERROR: Job failed: exit code 1