You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the outputs.tags gives a list of all the tags that were pushed. It would be useful if when, for example, a tag-sha is true, there was an outputs.tag-sha to accompany it. This would enable later steps to use a particular tag.
The motivation for this is a building an image of an application and picking a particular tag to use for generating a PR to bump the image tag in a Helm chart values.yaml
The text was updated successfully, but these errors were encountered:
All things considered I don't see how we could handle this behavior cause inputs from v1 have been merged to tags input in v2. Maybe you could use the version output which is the main tag. I'm closing this issue but feel free to leave a comment if you want a better alternative.
I think this solves what you are trying to do. I think the tag list follows the meta tags list order so if you put your ref tag first... ${{ fromJson(steps.dockermeta.outputs.json).tags[0]
Currently, the
outputs.tags
gives a list of all the tags that were pushed. It would be useful if when, for example, atag-sha
istrue
, there was anoutputs.tag-sha
to accompany it. This would enable later steps to use a particular tag.The motivation for this is a building an image of an application and picking a particular tag to use for generating a PR to bump the image tag in a Helm chart
values.yaml
The text was updated successfully, but these errors were encountered: