step execution failed: step 3 met error threshold of 1: failed to run step "helm-update-chart": failed to update chart dependencies: could not find protocol handler for: alias

[david-curran-90]

Checklist

• [ *] I've searched the issue queue to verify this is not a duplicate bug report.
• [ *] I've included steps to reproduce the bug.
• [ *] I've pasted the output of kargo version.
• [ *] I've pasted logs, if applicable.

Description

We use aliases in our helm Chart.yaml

dependencies:
  - name: my-chart
     version: 1.22.0
     repository: alias:dr

In the promotion tasks we are doing this to update the chart

  steps:
  - uses: helm-update-chart
    config:
      path: ${{ vars.appGitPath }}/${{ vars.appHelmPath }}
      charts:
      - repository: alias:dr
        name: my-chart
        version: 1.22.0

However this causes an issue in Kargo

failed to run step "helm-update-chart": failed to update chart dependencies: could not find protocol handler for: alias

I have tried using just the alias name dr and also escaping alias\:dr but these just cause issues with not being able to find any entry for the dependency

failed to run step "helm-update-chart": no dependency in Chart.yaml matched update with repository dr and name

Steps to Reproduce

• Use a helm chart with an alias in the dependency
• Use the helm-update-chart step to update the dependency

Version

1.4.0

[hiddeco]

The root issue is that repository aliases are environment-specific and not portable between systems. When you define alias:dr in your Chart.yaml, that alias is resolved through your local Helm configuration. However, Kargo runs in its own environment where these aliases aren't defined.

Because of this, the equivalent of running helm dep update after replacing the chart version fails (as presented in the could not find protocol handler for: alias error).

Given these constraints, the best option is to avoid using repository aliases entirely in your Helm charts. Instead, use the full repository URLs in both your Chart.yaml and Kargo configuration. This ensures compatibility across both local development and automated workflows, avoiding the portability issues inherent with repository aliases.

[github-actions]

This issue has been automatically marked as stale because it had no activity for 90 days. It will be closed if no activity occurs in the next 30 days but can be reopened if it becomes relevant again.