Merge remote-tracking branch 'community/master' into gcp-fix-system-workflow-behaviour

# Conflicts:
#	provider/workflow-gcp/src/main/java/org/opengroup/osdu/workflow/provider/gcp/osm/repository/
#	provider/workflow-gcp/src/main/java/org/opengroup/osdu/workflow/provider/gcp/repository/
3 jobs for !198 with gcp-fix-system-workflow-behaviour in 14 seconds (queued for 4 seconds)
latest detached
Status Name Job ID Coverage
failed deprecated-aws-include #730301
osdu-small allowed to fail


failed trigger-trusted-tests #730302


skipped osdu-gcp-helm-charts #730303
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-gcp-fix-system-workflow-behaviour', 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,
Cleaning up file based variables
ERROR: Job failed: exit code 1
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:0a97eee8041e2b6c0e65abb2700b0705d0da5525ca69060b9e0bde8a3d17afdb for alpine:latest with digest alpine@sha256:635f0aa53d99017b38d1a0aa5b2082f7812b03e3cdb299103fe77b5c8a07f1d2 ...
The AWS includes now support different build environments, which should be specified directly. Consider using: aws-global.yml, and either aws-maven.yml or aws-python.yml
$ /bin/false
Cleaning up file based variables
ERROR: Job failed: exit code 1