actions/attest
1
0
Fork 0
Code Issues Pull Requests Actions 268 Packages Projects Releases Wiki Activity

readme updates (#16)

Browse Source 
Signed-off-by: Brian DeHamer <[email protected]>
This commit is contained in:
Brian DeHamer
2024-02-28 13:56:23 -08:00
committed by GitHub
parent 32049315c5
commit 2246042d69
2 changed files with 113 additions and 158 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/linters/tsconfig.json
+1 -4
View File
@@ -5,8 +5,5 @@
"noEmit": true "noEmit": true
}, },
"include": ["../../__tests__/**/*", "../../src/**/*"], "include": ["../../__tests__/**/*", "../../src/**/*"],
"exclude": ["../../dist", "../../node_modules", "../../coverage", "*.json"], "exclude": ["../../dist", "../../node_modules", "../../coverage", "*.json"]
"references": [
{ "path": "./packages/attest" }
]
} }
README.md
+110 -152
View File
@@ -1,143 +1,125 @@
# attest # `actions/attest`
GitHub Action to sign and upload [in-toto Attestation Predicates][0] for Generate signed attestations for workflow artifacts. Internally powered by the
artifacts as part of a workflow. [@actions/attest][1] package.
Attestations bind some subject (a named artifact along with its digest) to a
predicate (some assertion about that subject) using the [in-toto][2] format.
[Predicates][3] consist of a type URI and a JSON object containing
type-dependent parameters.
A verifiable signature is generated for the attestation using a short-lived
[Sigstore][4]-issued signing certificate. If the repository initiating the
GitHub Actions workflow is public, the public-good instance of Sigstore will be
used to generate the attestation signature. If the repository is
private/internal, it will use the GitHub private Sigstore instance.
Once the attestation has been created and signed, it will be uploaded to the GH
attestations API and associated with the repository from which the workflow was
initiated.
Attestations can be verified using the `attestation` command in the [GitHub
CLI][5].
## Usage ## Usage
Within the GitHub Actions workflow which builds some artifact you would like to Within the GitHub Actions workflow which builds some artifact you would like to
attest, attest:
1. Ensure that the following permissions are set: 1. Ensure that the following permissions are set:
```yaml ```yaml
permissions: permissions:
id-token: write id-token: write
contents: write contents: write # TODO: Update this
``` ```
The `id-token` permission gives the action the ability to mint the OIDC token The `id-token` permission gives the action the ability to mint the OIDC
necessary to request a Sigstore signing certificate. The `contents` token necessary to request a Sigstore signing certificate. The `contents`
permission is necessary to persist the attestation. permission is necessary to persist the attestation.
> **NOTE**: The set of required permissions will be refined in a future 1. Add the following to your workflow after your artifact has been built:
> release.
1. After your artifact build step, add the following:
```yaml ```yaml
- uses: actions/attest@main - uses: actions/attest@v1
with: with:
predicate-path: './predicate.json' subject-path: '<PATH TO ARTIFACT>'
predicate-type: 'https://in-toto.io/attestation/release/v0.1' predicate-type: '<PREDICATE URI>'
subject-path: '${{ github.workspace }}/PATH_TO_FILE' predicate-path: '<PATH TO PREDICATE>'
``` ```
The `subject-path` parameter should identity the artifact for which you want The `subject-path` parameter should identity the artifact for which you want
to generate an attestation. to generate an attestation. The `predicate-type` can be any of the the
[vetted predicate types][3] or a custom value. The `predicate-path`
### What is being attested? identifies a file containg the JSON-encoded predicate parameters.
The generated attestation is based on the inputs of `predicate-path` and `predicate-type`
```json
{
"_type": "https://in-toto.io/Statement/v1",
"subject": [
{
"name": "subject",
"digest": {
"sha256": "7d070f6b64d9bcc530fe99cc21eaaa4b3c364e0b2d367d7735671fa202a03b32"
}
}
],
"predicateType": $predicateType,
"predicate": {
...
}
}
```
The predicate statement is signed with a short-lived, [Sigstore][1]-issued
certificate.
If the repository initiating the GitHub Actions workflow is public, the public
instance of Sigstore will be used to generate the attestation signature. If the
repository is private, it will use the GitHub private Sigstore instance.
### Where does the attestation go?
On the actions summary page for a repository you'll see an "Attestations" link
which will take you to a list of all the attestations generated by workflows in
that repository.
![Actions summary view](./.github/attestations.png)
### How are attestations verified?
Attestations can be verified using the [gh-attestation][2] extension for the
[GitHub CLI][3].
## Customization
See [action.yml](action.yml)
### Inputs ### Inputs
- `predicate` - String containing the value for the attestation predicate. See [action.yml](action.yml)
Must supply exactly one of "predicate-path" or "predicate". ```yaml
- uses: actions/attest@v1
with:
# Path to the artifact serving as the subject of the attestation. Must
# specify exactly one of "subject-path" or "subject-digest".
subject-path:
- `predicate-path` - Path to the file which contains the content for the # SHA256 digest of the subject for for the attestation. Must be in the form
attestation predicate. # "sha256:hex_digest" (e.g. "sha256:abc123..."). Must specify exactly one
# of "subject-path" or "subject-digest".
subject-digest:
Must supply exactly one of "predicate-path" or "predicate". # Subject name as it should appear in the attestation. Required unless
# "subject-path" is specified, in which case it will be inferred from the
# path.
subject-name:
- `predicate-type` - URI identifying the type of the predicate. # URI identifying the type of the predicate.
predicate-type:
- `subject-path` - Path to the artifact for which the predicate statement will be # JSON string containing the value for the attestation predicate. Must
generated. # supply exactly one of "predicate-path" or "predicate".
predicate:
Must specify exactly one of `subject-path` or `subject-digest`. Wildcards can # Path to the file which contains the JSON content for the attestation
be used to identify more than one artifact. # predicate. Must supply exactly one of "predicate-path" or "predicate".
predicate-path:
- `subject-digest` - Digest of the subject for which the predicate statement # Whether to push the attestation to the image registry. Requires that the
will be generated. # "subject-name" parameter specify the fully-qualified image name and that
# the "subject-digest" parameter be specified. Defaults to false.
push-to-registry:
Only SHA-256 digests are accepted and the supplied value must be in the form # The GitHub token used to make authenticated API requests. Default is
"sha256:\<hex-encoded-digest\>". Must specify exactly one of `subject-path` or # ${{ github.token }}
`subject-digest`. github-token:
```
- `subject-name` - Subject name as it should appear in the predicate statement.
Required when the subject is identified by the `subject-digest` parameter.
When attesting container images, the name should be the fully qualified image
name.
- `push-to-registry` - If true, the signed attestation is pushed to the
container registry identified by the `subject-name`. Default: `false`.
- `github-token` - Token used to make authenticated requests to the GitHub API.
Default: `${{ github.token }}`.
The supplied token must have the permissions necessary to write attestations
to the repository.
### Outputs ### Outputs
- `bundle-path` - The file path of JSON-serialized [Sigstore bundle][4] <!-- markdownlint-disable MD013 -->
containing the attestation and related verification material.
## Sample Workflows | Name | Description | Example |
| ------------- | -------------------------------------------------------------- | ----------------------- |
| `bundle-path` | Absolute path to the file containing the generated attestation | `/tmp/attestaion.jsonl` |
### Identify Artifact by Path <!-- markdownlint-enable MD013 -->
For the basic use case, simply add the `attest` action to Attestations are saved in the JSON-serialized [Sigstore bundle][6] format.
your workflow and supply the path to the artifact for which you want to generate
attestation. If multiple subjects are being attested at the same time, each attestation will
be written to the output file on a separate line (using the [JSON Lines][7]
format).
## Examples
### Identify Subject by Path
For the basic use case, simply add the `attest` action to your workflow and
supply the path to the artifact for which you want to generate attestation.
```yaml ```yaml
name: attest name: build-attest
on: on:
workflow_dispatch: workflow_dispatch:
@@ -152,63 +134,35 @@ jobs:
- name: Checkout - name: Checkout
uses: actions/checkout@v4 uses: actions/checkout@v4
- name: Build artifact - name: Build artifact
run: make some-app run: make my-app
- name: Attest - name: Attest
uses: actions/attest@main uses: actions/attest@v1
with: with:
predicate: | subject-path: '${{ github.workspace }}/my-app'
'{ "purl": $YOUR_PURL, "releaseId": $YOUR_RELEASE_ID }' predicate-type: 'https://example.com/predicate/v1'
predicate-type: 'https://in-toto.io/attestation/release/v0.1' predicate: '{}'
subject-path: '${{ github.workspace }}/some-app'
``` ```
### Identify Artifacts by Wildcard ### Identify Subjects by Wildcard
If you are generating multiple artifacts, you can generate attest for If you are generating multiple artifacts, you can generate an attestation for
each artifact by using a wildcard in the `subject-path` input. each by using a wildcard in the `subject-path` input.
```yaml ```yaml
name: build-wildcard-with-attest - uses: actions/attest@v1
on:
workflow_dispatch:
jobs:
build:
permissions:
id-token: write
contents: write
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Set up Go
uses: actions/setup-go@v4
- name: Run GoReleaser
uses: goreleaser/goreleaser-action@v5
with: with:
distribution: goreleaser
version: latest
args: release --clean
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Attest artifact
uses: actions/attest@main
with:
predicate: |
'{ "purl": $YOUR_PURL, "releaseId": $YOUR_RELEASE_ID }'
predicate-type: 'https://in-toto.io/attestation/release/v0.1'
subject-path: 'dist/**/my-bin-*' subject-path: 'dist/**/my-bin-*'
predicate-type: 'https://example.com/predicate/v1'
predicate: '{}'
``` ```
For supported wildcards along with behavior and documentation, see For supported wildcards along with behavior and documentation, see
[@actions/glob][5] which is used internally to search for files. [@actions/glob][8] which is used internally to search for files.
### Container Image ### Container Image
When working with container images you may not have a `subject-path` value you When working with container images you can invoke the action with the
can supply. In this case you can invoke the action with the `subject-name` and `subject-name` and `subject-digest` inputs.
`subject-digest` inputs.
If you want to publish the attestation to the container registry with the If you want to publish the attestation to the container registry with the
`push-to-registry` option, it is important that the `subject-name` specify the `push-to-registry` option, it is important that the `subject-name` specify the
@@ -220,7 +174,7 @@ the specific image being attested is identified by the supplied digest.
> registry portion of the image name. > registry portion of the image name.
```yaml ```yaml
name: build-image-with-attest name: build-attested-image
on: on:
push: push:
@@ -254,19 +208,23 @@ jobs:
push: true push: true
tags: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:latest tags: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:latest
- name: Attest - name: Attest
uses: actions/attest@main uses: actions/attest@v1
id: attest id: attest
with: with:
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
subject-digest: ${{ steps.push.outputs.digest }} subject-digest: ${{ steps.push.outputs.digest }}
predicate: |
'{ "purl": $YOUR_PURL, "releaseId": $YOUR_RELEASE_ID }'
predicate-type: 'https://in-toto.io/attestation/release/v0.1' predicate-type: 'https://in-toto.io/attestation/release/v0.1'
predicate: '{"purl":"pkg:oci/..."}'
push-to-registry: true
``` ```
[0]: https://github.com/in-toto/attestation/blob/main/spec/predicates/README.md [1]: https://github.com/actions/toolkit/tree/main/packages/attest
[1]: https://www.sigstore.dev/ [2]: https://github.com/in-toto/attestation/tree/main/spec/v1
[2]: https://github.com/github-early-access/gh-attestation [3]:
[3]: https://cli.github.com/ https://github.com/in-toto/attestation/tree/main/spec/predicates#in-toto-attestation-predicates
[4]: https://github.com/sigstore/protobuf-specs/blob/main/protos/sigstore_bundle.proto [4]: https://www.sigstore.dev/
[5]: https://github.com/actions/toolkit/tree/main/packages/glob#patterns [5]: https://cli.github.com/
[6]:
https://github.com/sigstore/protobuf-specs/blob/main/protos/sigstore_bundle.proto
[7]: https://jsonlines.org/
[8]: https://github.com/actions/toolkit/tree/main/packages/glob#patterns