Skip to content
This repository has been archived by the owner on Jul 5, 2021. It is now read-only.

Push 'latest' tagged images #146

Open
1aziz opened this issue Jan 13, 2021 · 0 comments
Open

Push 'latest' tagged images #146

1aziz opened this issue Jan 13, 2021 · 0 comments

Comments

@1aziz
Copy link
Contributor

1aziz commented Jan 13, 2021

Describe the solution you'd like
Currently, we're pushing images tagged with the PR number, SHA or the master branch name (based on the trigger types
and conditions defined in the prep step).
However, we don't have any additional conditions for triggers related to master / release tags, therefore the latest tag has been remained unchanged and containersol/externalsecret-operator:latest is no longer the same as containersol/externalsecret-operator:master or any other latest tagged-release.

What is the added value?
Offering a consistent 'latest' tag helps people to run the controller deployment using the default settings in our Makefile. Using a latest tag could be useful for demo and testing purposes.

Give us examples of the outcome
We will need to provide a new condition in the prep step adding a new value to the TAGS (outputted as tags in the pipeline).

@1aziz 1aziz assigned 1aziz and unassigned 1aziz Jan 13, 2021
amouat pushed a commit that referenced this issue May 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant