This message was deleted.
# general
s
This message was deleted.
b
you can work around it by doing
helm registry login
before running pulumi
f
i've tried that but i couldnt :c, before running that Release i'm executing (with subprocess.run and inside the pulumi_program()):
Copy code
"helm registry login {registry_url} -u {auth_token.user_name} -p {auth_token.password}"
i don't know if its something about the workspaces or something like that
At the moment im pulling the chart to local, use it to execute the Release and delete it after that. It works but its awful
m
Not sure about ECR but could you work with a IAM role? I know that in Azure you have the Pull role for images from ACR
f
• Solved Finally i solved it by setting "helm_release_setting" argument with the registry-config path hardcoded, probably the "helm registry login" and this config where targeting different paths for the registry config.
Copy code
"helm registry login {registry_url} -u {auth_token.user_name} -p {auth_token.password} --registry-config {path}"

k8s.ProviderArgs(
    kubeconfig=kubeconfig,
    helm_release_settings=k8s.HelmReleaseSettingsArgs(
        registry_config_path=path
        )
    ),
Thanks =D
🙌 1