gh-action-sigstore-python - GitHub Marketplace (original) (raw)

CI Self-test

This GitHub Action uses sigstore-pythonto generate Sigstore signatures. gh-action-sigstore-python is the easiest way to integrate Sigstore into your CI system and can be used for not only Python projects, but projects in other languages as well.

Important

Are you publishing a package to PyPI? If so, you do not need this action:pypa/gh-action-pypi-publishwill handle signing for you!

Index

Usage

Simply add sigstore/gh-action-sigstore-python to one of your workflows:

jobs: selftest: runs-on: ubuntu-latest permissions: id-token: write steps: - uses: actions/checkout@v4 with: persist-credentials: false - name: install run: python -m pip install . - uses: sigstore/gh-action-sigstore-python@v3.0.0 with: inputs: file.txt

Note: Your workflow must have permission to request the OIDC token to authenticate with. This can be done by setting id-token: write on your job (as above) or workflow.

More information about permission settings can be foundhere.

Configuration

gh-action-sigstore-python takes a variety of configuration inputs, most of which are optional.

inputs

The inputs setting controls what files sigstore-python signs. At least one input must be provided unless release-signing-artifacts is set to true on release events.

To sign one or more files:

The inputs argument also supports file globbing:

Multiple lines are fine, and whitespace in filenames can also be escaped using POSIX shell lexing rules:

Note

In versions of this action before 2.0.0, the inputs setting allowed for shell expansion. This was unintentional, and was removed with 2.0.0.

identity-token

Default: Empty (the GitHub Actions credential will be used)

The identity-token setting controls the OpenID Connect token provided to Fulcio. By default, the workflow will use the credentials found in the GitHub Actions environment.

oidc-client-id

Default: sigstore

The oidc-client-id setting controls the OpenID Connect client ID to provide to the OpenID Connect Server during OAuth2.

Example:

oidc-client-secret

Default: Empty (no OpenID Connect client secret provided by default)

The oidc-client-secret setting controls the OpenID Connect client secret to provide to the OpenID Connect Server during OAuth2.

Example:

staging

Default: false

The staging setting controls whether or not sigstore-python uses sigstore's staging instances, instead of the default production instances.

Example:

verify

Default: false

The verify setting controls whether or not the generated signatures and certificates are verified with the sigstore verify subcommand after all files have been signed.

This is not strictly necessary but can act as a smoke test to ensure that all signing artifacts were generated properly and the signature was properly submitted to Rekor.

If verify is enabled, then you must also pass the verify-cert-identityand verify-oidc-issuer settings. Failing to pass these will produce an error.

Example:

verify-cert-identity

Default: Empty

The verify-cert-identity setting controls whether to verify the Subject Alternative Name (SAN) of the signing certificate after signing has taken place. If it is set, sigstore-python will compare the certificate's SAN against the provided value.

This setting only applies if verify is set to true. Supplying it without verify: truewill produce an error.

This setting may only be used in conjunction with verify-oidc-issuer. Supplying it without verify-oidc-issuer will produce an error.

verify-oidc-issuer

Default: https://oauth2.sigstore.dev/auth

The verify-oidc-issuer setting controls whether to verify the issuer extension of the signing certificate after signing has taken place. If it is set, sigstore-python will compare the certificate's issuer extension against the provided value.

This setting only applies if verify is set to true. Supplying it without verify: truewill produce an error.

This setting may only be used in conjunction with verify-cert-identity. Supplying it without verify-cert-identity will produce an error.

Example:

upload-signing-artifacts

Default: false

The upload-signing-artifacts setting controls whether or not sigstore-python createsworkflow artifactsfor the outputs produced by signing operations.

By default, no workflow artifacts are uploaded. When enabled, the default workflow artifact retention period is used.

Example:

release-signing-artifacts

Default: true

The release-signing-artifacts setting controls whether or not sigstore-pythonuploads signing artifacts to the release publishing event that triggered this run. This setting has no effect on non-release events.

If enabled, this setting also re-uploads and signs GitHub's default source code artifacts, as they are not guaranteed to be stable.

Requires the contents: write permission.

Example:

permissions: contents: write

...

On release events, it is also valid to have no explicit inputs. When used on release events, this action will sign any pre-existing release artifacts:

permissions: contents: write

...

no explicit settings needed, signs all pre-existing release artifacts

Internal options

⚠️ Internal options ⚠️

Everything below is considered "internal," which means that it isn't part of the stable public settings and may be removed or changed at any points. You probably do not need these settings.

All internal options are prefixed with internal-be-careful-.

internal-be-careful-debug

Default: false

The internal-be-careful-debug setting enables additional debug logs, both within sigstore-python itself and the action's harness code. You can use it to debug troublesome configurations.

Example:

Licensing

gh-action-sigstore-python is licensed under the Apache 2.0 License.

Code of Conduct

Everyone interacting with this project is expected to follow thesigstore Code of Conduct

Security

Should you discover any security issues, please refer to sigstore's security process.

Info

gh-action-sigstore-python is developed as part of the sigstore project.

We also use a slack channel! Click here for the invite link.