Azure / Azure/Azure-Verified-Modules
[Documentation Update]:docs/content/contributing/bicep/bicep-contribution-flow/_index.md
- Dominant language
- PowerShell
- Stars
- 580
- Forks
- 161
- Avg merge
- 11h 3m
- Merged PRs (30d)
- 15
Description
### Check for previous/existing GitHub issues
- [x] I have checked for previous/existing GitHub issues
### Description
In docs/content/contributing/bicep/bicep-contribution-flow/_index.md
The TOKEN_NAMEPREFIX cannot be more then 4 characters.
Because the avm.res.compute.virtual-machine workflow will also create a VM with SSDv2 disks and the name of the VM will be cvmwinssdv2, so with a nameprefix of 5 characters the name will exceed the 15 character limit.
`[{"code":"InvalidParameter","target":"osProfile.computerName","message":"Windows computer name cannot be more than 15 characters long, be entirely numeric, or contain the following characters: ` ~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \\ | ; : . ' \" , < > / ?."}]}`
I would suggest limiting it to 3 characters max.
Contributor guide
No contributing guide indexed for this repository
Research direction
Open docs/content/contributing/bicep/bicep-contribution-flow/_index.md and review the TOKEN_NAMEPREFIX guidance alongside the documented avm.res.compute.virtual-machine naming. Update the stated limit so the generated Windows VM name remains within the 15-character limit, then verify the example and wording are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100