Upgrade azure/aks-set-context
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
- Upgrade
azure/aks-set-contexttov3
Details
Error message when deploying using v3:
Warning: Unexpected input(s) 'creds', valid inputs are ['resource-group', 'cluster-name', 'subscription', 'admin', 'use-kubelogin']
Run azure/aks-set-context@main
with:
creds: ***
resource-group: ACMI_***
cluster-name: ***-prod
admin: false
use-kubelogin: false
env:
DOCKER_USERNAME: ***
DOCKER_PASSWORD: ***
DOCKER_REPOSITORY: ***labs/***-api
DOCKER_IMAGE_TAG: dda1c019d6f6e384849932d7ca087f424b0d376c
CONTEXT: ***-prod
K8S_ENV: xos-api-stg
DEPLOY_TAG: staging
IMAGE_TAG: latest
IMAGE_NAME: ACMILabs/***-api
Error: File not found: '/home/runner/work/_actions/azure/aks-set-context/main/lib/index.js'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository's GitHub Actions workflow that runs the deployment and inspect its azure/aks-set-context configuration. Compare the configured inputs with the v3 inputs shown in the issue and check the action's generated-file error. Done means the deployment workflow uses v3 without unexpected-input or missing-file errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions
- Domain
- ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100