Function that creates an abbreviation for a location
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
Given some naming recommendations for resources in Azure, it is very common to have the name or an abbreviation of the resource's location in its name. However this adds to the length of the resource name, I do understand the purpose and so I think it is a good idea to do so. However... Because some resources have a limited amount of characters you can use to name the resource, I also think it is a good idea to keep (sections of) the name somewhat short.
Therefore I think it adds value to add a function to bicep that accepts a `location` parameter as a string, and outputs an abbreviation for that location as a string, shortening the name to 3 or 4 characters (or maybe even shorter?).
I currently solve this by adding the location abbreviation as a parameter to my main bicep file, but using a central function that allows for shortening location names 'the standard' way really adds value if you ask me,
Contributor guide
Research direction
The issue does not name implementation files, tests, or an entry point. First clarify the standard abbreviation mapping, supported Azure locations, and expected collision and length behavior; done should be a documented function with coverage for the agreed mappings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100