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
Was there a decision why tags are ignored for stages_image_name?
The decision was made based on these facts:
For legacy behavior (no buildkit), the action does not know in advance how many stages are going to be crated, so it makes them up using -stages: . All we can do to have different tags per stage is to allow providing a custom prefix/suffix which I don't see that useful
For buildkit, only one cache image is needed, so I used latest as that felt like a sensible default but it's true it could be anything else. Not sure why latest would be an issue though
Was looking at the documentation and saw
Was there a decision why tags are ignored for
stages_image_name
?The text was updated successfully, but these errors were encountered: