-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: expose image manifest digest of all copied artifacts #1086
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,57 +1,18 @@ | ||
# oci-copy-oci-ta task | ||
|
||
Given an `oci-copy.yaml` file in the user's source directory, the `oci-copy` task will copy content from arbitrary urls into the OCI registry. | ||
|
||
It generates a limited SBOM and pushes that into the OCI registry alongside the image. | ||
|
||
It is not to be considered safe for general use as it cannot provide a high degree of provenance for artficats and reports them only as "general" type artifacts in the purl spec it reports in the SBOM. Use only in limited situations. | ||
Given a file in the user's source directory, copy content from arbitrary urls into the OCI registry. | ||
|
||
## Parameters | ||
|name|description|default value|required| | ||
|---|---|---|---| | ||
|IMAGE|Reference of the image buildah will produce.||true| | ||
|SOURCE_ARTIFACT|The trusted artifact URI containing the application source code.||true| | ||
|IMAGE|Reference of the image we will push||true| | ||
|OCI_COPY_FILE|Path to the oci copy file.|./oci-copy.yaml|false| | ||
|SOURCE_ARTIFACT|The Trusted Artifact URI pointing to the artifact with the application source code.||true| | ||
|
||
## Results | ||
|name|description| | ||
|---|---| | ||
|IMAGE_DIGEST|Digest of the image just built| | ||
|IMAGE_URL|Image repository where the built image was pushed| | ||
|
||
## oci-copy.yaml schema | ||
JSON schema for the `oci-copy.yaml` file. | ||
|IMAGES|URIs for all image manifests published, for signing| | ||
|IMAGE_DIGEST|Digest of the artifact just pushed| | ||
|IMAGE_URL|Repository where the artifact was pushed| | ||
|
||
```json | ||
{ | ||
"type": "object", | ||
"required": ["artifacts"], | ||
"properties": { | ||
"artifacts": { | ||
"type": "array", | ||
"items": { | ||
"type": "object", | ||
"required": ["source", "filename", "type", "sha256sum"], | ||
"properties": { | ||
"source": { | ||
"description": "URL of the artifact to copy", | ||
"type": "string" | ||
}, | ||
"filename": { | ||
"description": "Filename that should be applied to the artifact in the OCI registry", | ||
"type": "string" | ||
}, | ||
"type": { | ||
"description": "Media type that should be applied to the artifact in the OCI registry", | ||
"type": "string" | ||
}, | ||
"sha256sum": { | ||
"description": "Digest of the artifact to be checked before copy", | ||
"type": "string" | ||
} | ||
} | ||
} | ||
} | ||
} | ||
} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This imposes a pretty nasty limit on the number of images that this task can copy (before the result breaks the 4kb size limit). If the general expectation is that this task will be used for copying, say, 10 artifacts, we should be good. But maybe EC could (should it?) support signed index images referencing unsigned manifests?