We need to avoid fixing the tags in each environment (DEv, QA, Test, Main) in case of update or add new image for any soultion.
currently if we have a defected image on the HUB; and we need to update it; we do two steps:
1- update the image on the HUB itself
2- update the tag in the playground for each Env.
Implementation
we can use fixed suffix on all Environments playground. (Ex. TF-Caprover, TF-owncloud)
and we change the image name with this suffix only in the HUB.
By this we don't need to wait for the next release to have the image updated on all Environments.
Verified,
On all the networks, they are using the same latest version, and for the caprover issue, I just deployed an instance on the devnet, and it did use the latest caprover version.
Description
We need to avoid fixing the tags in each environment (DEv, QA, Test, Main) in case of update or add new image for any soultion. currently if we have a defected image on the HUB; and we need to update it; we do two steps: 1- update the image on the HUB itself 2- update the tag in the playground for each Env.
Implementation
By this we don't need to wait for the next release to have the image updated on all Environments.