Pushes an advisory yaml to a Git repository. The task will always exit 0 even if something fails. This is because the task result will not be set if the task fails, and the task result should always be set and propagated back to the cluster that creates the internal request. The success/failure is handled in the task creating the internal request.
| Name | Description | Optional | Default value |
|---|---|---|---|
| advisory_json | String containing a JSON representation of the advisory data (e.g. '{"product_id":123,"type":"RHSA"}') | No | - |
| componentGroup | ComponentGroup being released | No | - |
| origin | The origin workspace where the release CR comes from. This is used to determine the advisory path | No | - |
| config_map_name | The name of the configMap that contains the signing key | No | - |
| advisory_secret_name | The name of the secret that contains the advisory creation metadata | No | - |
| errata_secret_name | The name of the secret that contains the errata service account metadata | No | - |
| internalRequestPipelineRunName | Name of the PipelineRun that called this task | No | - |
| contentType | The contentType of the release artifact. One of [image | binary | generic |
| caTrustConfigMapName | The name of the ConfigMap to read CA bundle data from | Yes | trusted-ca |
| caTrustConfigMapKey | The name of the key in the ConfigMap that contains the CA bundle data | Yes | ca-bundle.crt |