The YAML schema for SignReleaseBundle native step is as follows:
An alphanumeric string (underscores are permitted) that identifies the step.
SignReleaseBundle for this step type.
Description of usage
| ||Must specify a ReleaseBundle resource whose ||Required|
Must specify a ReleaseBundle resource. This ReleaseBundle is updated with the
There is no additional configuration required.
Tags derived from Bash
All native steps derive from the Bash step. This means that all steps share the same base set of tags from Bash, while native steps have their own additional tags as well that support the step's particular function. So it's important to be familiar with the Bash step definition, since it's the core of the definition of all other steps.
GPG Signing Key Passphrase
Declares collections of shell command sequences to perform for pre- and post-execution phases:
|Tag||Description of usage||Required/Optional|
|Commands to execute in advance of the native operation||Optional|
|Commands to execute on successful completion||Optional|
|Commands to execute on failed completion||Optional|
|Commands to execute on any completion||Optional|
The actions performed for the
onExecute phase are inherent to this step type and may not be overridden.
The following example shows how to configure a SignReleaseBundle step.
Sign a Release Bundle
Signs a ReleaseBundle provided as an input.
How it Works
When you use the SignReleaseBundle native step in a pipeline, it performs the following functions in the background:
- curl $distUrl/api/v1/release_bundle/$releaseBundleName/$releaseBundleVersion/sign (sign the release bundle)
- write_output (update the output ReleaseBundle resource)