feat(artifacts): Default to latest tag if not provided #27253
Conversation
openshift-ci
bot
added
do-not-merge/work-in-progress
github-actions
bot
added
the
kind/api-change
ninja-quokka
force-pushed
the
add_default_tag
branch
3 times, most recently
from
63134b1 to
a36f9b8
Compare
|
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
This change implements a feature where podman artifacts will default to using the 'latest' tag if no tag is provided by the user. This aligns the behavior of artifacts with that of container images, providing a more consistent user experience. Fixes: containers#27083 Signed-off-by: Lewis Roy <[email protected]>
ninja-quokka
force-pushed
the
add_default_tag
branch
from
a36f9b8 to
728c5c0
Compare
|
I would like to see some system tests of E2E test. podman artifact create foobar /PATH/TO/object |
|
Why is this in Draft? What is it waiting for? |
|
/approve |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ninja-quokka, rhatdan The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2 participants
This change implements a feature where podman artifacts will default to using the 'latest' tag if no tag is provided by the user. This aligns the behavior of artifacts with that of container images, providing a more consistent user experience.
Fixes: #27083
Does this PR introduce a user-facing change?