Arcaflow Container Toolkit (Formerly Carpenter) Secrets

[jdowni000]

With the adoption of a recent PR that includes secrets as well as inputs in the Arcaflow Container Toolkit Reusable Workflow, all secrets must be used explicitly in the caller workflow instead of secrets: inherit as was done before for internal organizational repositories. With the adoption of secrets similar to inputs to allow our external users to consume the reusable workflow, this overwrites the secrets: inherit from the caller workflow. If you are receiving the log outputs that QUAY_USERNAME and QUAY_PASSWORD are not set or empty, and the workflow is failing to push, this could be why!

Example of job in caller workflow

  act:
    uses: arcalot/arcaflow-reusable-workflows/.github/workflows/act.yaml@main
    with:
      image_name: ${{ github.event.repository.name }}
      image_tag: 'latest'
      quay_img_exp: 'never'
      github_username: ${{ github.actor }}
      github_namespace: ${{ github.repository_owner }}
    secrets:
      QUAY_NAMESPACE: ${{ secrets.QUAY_NAMESPACE }}
      QUAY_USERNAME: ${{ secrets.QUAY_USERNAME }}
      QUAY_PASSWORD: ${{ secrets.QUAY_PASSWORD }}```