Auto DevOps can no longer use private Helm repositories for dependencies of a custom Helm chart
Summary
As users of Auto DevOps, we can no longer use private Helm repositories and a custom Helm chart within the repository as of gitlab-org/cluster-integration/auto-deploy-image@e1144e93.
Steps to reproduce
- Create an Auto DevOps repository with a custom Helm chart at
./chartas per https://docs.gitlab.com/ee/topics/autodevops/customize.html#custom-helm-chart - Configure the Helm chart to depend on a chart from an aliased repository (so that the repository can require authorisation)
- Configure the alias via
AUTO_DEVOPS_CHART_REPOSITORY*variables
Example Project
https://gitlab.com/p3650-tobago/virtual-service-map
What is the current bug behavior?
Releases will fail, because gitlab-org/cluster-integration/auto-deploy-image@e1144e93 prevents use of both a custom Helm chart at ./chart and a private repository for dependencies.
What is the expected correct behavior?
The AUTO_DEVOPS_CHART_REPOSITORY variables are not exclusive with presence of ./chart respected and the custom Helm repository added via helm repo add before helm dependency update. This was the behaviour before gitlab-org/cluster-integration/auto-deploy-image@e1144e93.
Output of checks
This bug happens on GitLab.com