There is a security vulnerability in SSH key-generation using GitKraken < v8.0.1. If you used this tool to create SSH keys, please update GitKraken and regenerate. If you need help with this, contact forum-support@opengroup.org

delete record_change_pubsub_endpoint default value

Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #607559
osdu-small allowed to fail

00:00:05

failed deprecated-gcp-pipeline #607558
allowed to fail

00:00:13

 
  Review
failed trigger-trusted-tests #607560
osdu-small

00:00:09

 
Name Stage Failure
failed
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-GONRG-3366-Develop-helm-config-map-and-helm-deployments-for-register-service', 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
failed
deprecated-gcp-pipeline .Pre
Reinitialized existing Git repository in /builds/osdu/platform/system/register/.git/
Checking out c940d8f6 as refs/merge-requests/115/head...

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ echo "$DEPRECATED_MSG"
The integration test environment previously managed by the cloud-providers/gcp.yml is no longer supported. Consider removing it from your .gitlab-ci.yml
$ /bin/false
ERROR: Job failed: exit code 1
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:14119a10abf4669e8cdbdff324a9f9605d99697215a0d21c360fe8dfa8471bab for alpine:latest with digest alpine@sha256:e1c082e3d3c45cccac829840a25941e679c25d438cc8412c2fa221cf1a824e6a ...
$ echo "$DEPRECATED_MSG"
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