The helm-ci orb currently doesn't run helm dependency build or update, so will fail if the chart being checked has any dependencies unless the dependencies were committed to the repo as well.
This is an issue when trying to use it to lint charts that use KMI provided charts as dependencies.
To enhance this to support KMI my suggestion is to:
switch to cimg/base:stable image
add the circleci/aws-ecr@7.2.0 and circleci/helm@2.0.0 orbs
run helm/install-helm-client to install the helm client
This should be backwards compatible.
To then handle dependencies via the KMI helm repo, the following env variables would need to be provided:
AWS_ACCESS_KEY_ID=<provided by #kaluza-managed-infra>
AWS_SECRET_ACCESS_KEY=<provided by #kaluza-managed-infra>
The helm-ci orb currently doesn't run
helm dependency buildorupdate, so will fail if the chart being checked has any dependencies unless the dependencies were committed to the repo as well.This is an issue when trying to use it to lint charts that use KMI provided charts as dependencies.
To enhance this to support KMI my suggestion is to:
cimg/base:stableimagecircleci/aws-ecr@7.2.0andcircleci/helm@2.0.0orbshelm/install-helm-clientto install the helm clientThis should be backwards compatible.
To then handle dependencies via the KMI helm repo, the following env variables would need to be provided:
AWS_ACCESS_KEY_ID=<provided by #kaluza-managed-infra>AWS_SECRET_ACCESS_KEY=<provided by #kaluza-managed-infra>AWS_REGION=eu-west-1AWS_ECR_ACCOUNT_URL=215727133225.dkr.ecr.eu-west-1.amazonaws.comHELM_EXPERIMENTAL_OCI=1To pull dependencies it would then need to:
aws-ecr/ecr-loginto login to ECRaws ecr get-login-password --region eu-west-1 | helm registry login --username AWS --password-stdin ${AWS_ECR_ACCOUNT_URL}to login to the KMI helm repohelm dependency buildorupdatebefore linting.I've implemented something like this for the
event-streaming-platform-kmi-gitopsrepo, and can prepare a PR for this too if there's interest.