search

DeployHubProject / DeployHub-Pro

DeployHub Pro Pipeline Status Project
https://www.openmakesoftware.com/application-release-automation-for-continuous-delivery/
Other
11 stars 4 forks source link

helm details capture issue #330

Open piyush94 opened 3 years ago

piyush94 commented 3 years ago

Currently, while capturing the helm details, in the manifest the "helmrepo" field is filled in using the "helmrepo.name" attribute. But in the component details in the chart field a different name can be specified and will work fine during deployment and also in helminfo.sh because both take the name from the component chart field and not helmrepo.name.

This mismatch causes an error during the processing of the manifest as the helm repo name is different from where the chart is actually located.

Can we enforce in some way for the two names to be the same?

piyush94 commented 3 years ago

Also, if the docker image is not coming from the docker hub and is being downloaded from a private docker registry and while capturing image details such as the image digest can DeployHub abort the further capture and deployment.

As the image digest value will be empty, it denotes that either the image name or tag, that has been provided, is incorrect.

We would like at DeployHub level itself to validate that the image details are correct or not and abort if incorrect.