Azure / Azure/Azure-Landing-Zones
Allow disabling the root_id prefix from custom role definitions names
- Dominant language
- PowerShell
- Stars
- 96
- Forks
- 70
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 7
Description
### Community Note
- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Description
Allow discarding the root_id prefix for custom role definitions.
#### Is your feature request related to a problem?
I'm part of a platform team which services product teams within my company. The custom role definitions we define and create via this module, are exposed to product teams. While the naming convention "[some-cryptic-root-id] real-resource-name" is useful for resources managed by the platform team, I would much prefer to use a prettier name without a prefix for custom role definitions consumed by product teams.
#### Describe the solution you'd like
Some input variable in the module which would disable the root_id prefix for custom role definition names.
#### Additional context
Contributor guide
Research direction
Start by locating the module logic that creates custom role definitions and applies the root_id prefix. Check how module inputs are defined and confirm that disabling the new option produces names without the prefix while preserving the current default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authorization, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100