docker / docker/metadata-action
Support for setting OCI-Metadata in Output Object
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 160
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 12
Description
Description
Hi there!
I'd like to trigger oci-metadata in the output json of the bake file. However, it seems like the best way to do this is to have the metadata action step render this.
Why? Because if I do it in the bake-file itself then it overrides the output of the Docker Metadata Bake Action. This could be troublesome since the value is a JSON array, seen here and it's not always certain which block is being merged when Docker Bake does a JSON Patch of the two objects.
So, it would be nice to have this as a flag in the Docker Metadata-Action.
Thoughts? As always, thank you and much appreciated!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Docker Metadata Bake Action's metadata rendering and output handling, then review Docker Bake's targetoutput and OCI media types documentation. Done means a new flag can add oci-metadata to the output JSON without unexpectedly replacing existing Docker Metadata Bake Action output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, typescript
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100