Relevant Naming For Resources
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points, so first clarify the naming rules and identify where resources and resource groups are created. Done means a documented, consistent convention is applied so generated names follow the requested pattern, including the example given.
Written by the indexing model from the issue text.
Description
We need to standardize the naming conventions for Resources and Resource Groups so that users can find their resources easier.
Ex: Rather than myResourceGroup4056 -> myLEMP_ResourceGroup4056
- Dominant language
- Go
- Stars
- 40
- Forks
- 27
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 1
Contributor guide
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/InnovationEngine
-
Azure/InnovationEngine#262 · 1 reaction · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/InnovationEngine#259 ·
-
bug enhancement
Difficulty 3/5 1-2 days Newbie friendliness 38/100
Azure/InnovationEngine#258 ·
-
enhancement innovation engine
Azure/InnovationEngine#256 · 1 reaction · 1 assignee ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
Azure/InnovationEngine#252 · 1 comment ·
All issues in Azure/InnovationEngine
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