Skip to content

Latest commit

 

History

History
33 lines (30 loc) · 8.99 KB

File metadata and controls

33 lines (30 loc) · 8.99 KB

rh-direct-sign-image

Task to create internalrequests to directly sign snapshot components

Parameters

Name Description Optional Default value
snapshotPath Path to the JSON string of the mapped Snapshot spec in the data workspace No -
dataPath Path to the JSON string of the merged data to use in the data workspace No -
requester Name of the user that requested the signing, for auditing purposes No -
requestTimeout InternalRequest timeout Yes 1800
concurrentLimit The maximum number of signing requests to run in parallel Yes 8
pipelineRunUid The uid of the current pipelineRun. Used as a label value when creating internal requests No -
pyxisServer The server type to use. Options are 'production','production-internal','stage-internal' and 'stage' Yes production
pyxisSecret The kubernetes secret to use to authenticate to Pyxis. It needs to contain two keys: key and cert No -
batchLimit size of batch attributes to send to internal-request. As internal request arguments are need to be strings, size here represent maximal string length of references and manifest_digests sent to internal request Yes 15000
signRegistryAccessPath The relative path in the workspace to a text file that contains a list of repositories that needs registry.access.redhat.com image references to be signed (i.e. requires_terms=true), one repository string per line, e.g. "rhtas/cosign-rhel9" No -
ociStorage The OCI repository where the Trusted Artifacts are stored Yes empty
ociArtifactExpiresAfter Expiration date for the trusted artifacts created in the OCI repository. An empty string means the artifacts do not expire Yes 1d
trustedArtifactsDebug Flag to enable debug logging in trusted artifacts. Set to a non-empty string to enable Yes ""
orasOptions oras options to pass to Trusted Artifacts calls Yes ""
sourceDataArtifact Location of trusted artifacts to be used to populate data directory Yes ""
dataDir The location where data will be stored Yes /var/workdir/release
taskGitUrl The url to the git repo where the release-service-catalog tasks and stepactions to be used are stored No -
taskGitRevision The revision in the taskGitUrl repo to be used No -
signingRepo Git repository URL containing the signing tasks Yes https://gitlab.cee.redhat.com/signing/signing.git
signingRevision Git revision (branch, tag, or commit) in the signing repository Yes main
signPipeline Name of the internal pipeline to use for container signing Yes container-signing
signPipelineServiceAccount Service account to use for the signing pipeline Yes signing-pipeline-sa
pipelineImage The image to use for the signing pipeline Yes quay.io/konflux-ci/signing:latest
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