microsoft / microsoft/template-validation-action

template-validation-action doesn't work as expected when validating sample using aks and helm

Open
#69 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
24
Forks
11
Avg merge
17h 10m
Merged PRs (30d)
1

Description

Issue report

What the template-validation-action-sample does is provision an aks cluster and then deploy a helm chart in the cluster.
I can easily run azd up locally, and run successfully.

  • Image

But if I use microsoft/template-validation-action@v0.3.5 to validate my sample, it comes with the error.

ERROR: error executing step command 'deploy --all': failed deploying service 'jupyterhub': helm deployment failed: failed to add repo jupyterhub: exit code: 1, stdout: , stderr: Error: mkdir /home/runner: permission denied

Please check the workflow's output summary.

How to reproduce

  1. For this template-validation-action-sample to reproduce the issue
  2. Set the required Repository variables to run the validation-sample-workflow.yml
    • Image
  3. Run the workflow.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the template-validation-action-sample workflow, especially .github/workflows/validation-sample-workflow.yml, and review the linked workflow run output. Reproduce the validation with the AKS and Helm deployment, then trace why the action's Helm repository setup attempts to create /home/runner. Done means the sample validates successfully through the workflow without the permission error.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, github-actions, helm, kubernetes
Domain
ci-cd, cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.