When we implemented the creation of Helm packages for deploying Pipelines bundled with Tasks, we templated the version of the Task component images so that the user can define them on the fly when deploying the pipeline package. We have moved away from deploying Tasks along with Pipelines, and we are now packaging all Tasks in one Helm package for every new Dracon release. This means that we can now pin the image version to the version of Dracon for which we are building the Helm package. We can replace the Helm template in all Tasks with latest and replace it programmatically in the code used by the draconctl components package command.
When we implemented the creation of Helm packages for deploying Pipelines bundled with Tasks, we templated the version of the Task component images so that the user can define them on the fly when deploying the pipeline package. We have moved away from deploying Tasks along with Pipelines, and we are now packaging all Tasks in one Helm package for every new Dracon release. This means that we can now pin the image version to the version of Dracon for which we are building the Helm package. We can replace the Helm template in all Tasks with
latestand replace it programmatically in the code used by thedraconctl components packagecommand.