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

Added both the methods (with and without storage account name argument)

1 job for !108 with multiPartitionSupportWorkflowIngestion in 1 minute and 52 seconds (queued for 1 second)
latest detached
Status Name Job ID Coverage
failed trigger-trusted-tests #380594


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-multiPartitionSupportWorkflowIngestion', 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