Skip to content

Latest commit

 

History

History
45 lines (34 loc) · 2.55 KB

File metadata and controls

45 lines (34 loc) · 2.55 KB

publish-image

Manifest: publish-image/action.yml

This action signs and publishes a single container image to the given registry. It does the following work:

  1. Tag the source-image-uri with the specified image-registry-uti, image-repository, and image-repository.
  2. Push the container image to the specified registry.
  3. Sign the container image (which pushes the signature to the specified registry).
  4. Generate a CycloneDX SBOM via a syft scan and merge its components.
  5. Convert the merged CycloneDX SBOM to SPDX (normalising deprecated license ids).
  6. Attest the image with both the CycloneDX and SPDX SBOMs as predicates (which pushes the attestations to the specified registry).

Inputs and Outputs

Tip

For descriptions of the inputs and outputs, see the complete publish-image action.

Important

For multi-arch images, the image-manifest-tag should have the -$ARCH suffix, as the tag without it should be reserved for the image index manifest which will refer to container images for each architecture we will push images for.

Inputs

Input Required (Default) Description
image-registry-uri Yes The image registry URI, eg oci.stackable.tech
image-registry-username Yes The username used to access the image registry
image-registry-password Yes The password used to access the image registry
image-repository Yes The path to the image, eg sdp/kafka
image-manifest-tag Yes Human-readable tag with architecture information, eg 3.4.1-stackable0.0.0-dev-amd64
source-image-uri Yes The source image uri, which gets re-tagged by this action, eg localhost/kafka:...
cosign-retries No (3) The number of times cosign operations should be retried
cosign-retry-timeout No (30s) Duration to wait before a new cosign operation is retried, format: NUMBER[SUFFIX]

Outputs

None