When will 2.1 be deployed to Fairfax?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
No file, test, or entry point is named. Start by reviewing how this repository publishes versioned custom script extensions to public Azure, then determine the status of version 2.1 in Fairfax; done means the deployment status or planned timing is documented.
Written by the indexing model from the issue text.
Description
We are relying on the 2.1 version of linux custom script extension in public Azure. When do you plan to deploy 2.1 to Fairfax?
- Dominant language
- Go
- Stars
- 113
- Forks
- 46
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 3
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.
More from Azure/custom-script-extension-linux
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Azure/custom-script-extension-linux
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100