You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The helm-ci orb currently doesn't run
helm dependency build
orupdate
, 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:stable
imagecircleci/[email protected]
andcircleci/[email protected]
orbshelm/install-helm-client
to 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-1
AWS_ECR_ACCOUNT_URL=215727133225.dkr.ecr.eu-west-1.amazonaws.com
HELM_EXPERIMENTAL_OCI=1
To pull dependencies it would then need to:
aws-ecr/ecr-login
to 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 build
orupdate
before linting.I've implemented something like this for the
event-streaming-platform-kmi-gitops
repo, and can prepare a PR for this too if there's interest.The text was updated successfully, but these errors were encountered: