Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

💡 Feature Request - Descriptive module for creating security groups and mapping them to the custom roles through the roleAssignments module #389

Open
reduards opened this issue Nov 18, 2022 · 1 comment
Labels
Area: RBAC 🛂 Issues / PR's related to RBAC Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Enhancement ✨ New feature or request Type: Upstream Dependency ⬆️ something must happen before start something else

Comments

@reduards
Copy link

reduards commented Nov 18, 2022

Describe the solution you'd like

I would like to see a more descriptive way of creating security groups or mapping existing security groups to the customer roles and the right scope. We currently have a module for role assignment but no recommended path to utlize it in the intial deployment.

  1. Create module or sub module (leverage by orchestration) to create security groups

  2. Have an deployment example at roleAssignment module where these groups get mapped to corresponding custom role (NetOps for example) at a/the recommended scope.

Additional context

If you believe that this is a good idea, I am more than willing to help with this work.

EDIT: Just realised that creating Azure AD security groups with bicep is not supported. However, maybe we can leave a snippet with how to do it with PowerShell (New-AzureADGroup) similiar to how we show them how to retrieve object ID of an existing security group/spn/managed identity.

Best Regards,
Rasmus

@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label Nov 18, 2022
@jtracey93
Copy link
Collaborator

Hey @reduards,

As you have noticed creating AAD objects with Bicep is not yet supported. However, soon it hopefully will be.

Therefore I think we will place this one on long term hold until we see the AAD functionality come for Bicep.

Thanks

Jack

@jtracey93 jtracey93 added Area: RBAC and removed Needs: Triage 🔍 Needs triaging by the team labels Nov 21, 2022
@oZakari oZakari added Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Upstream Dependency ⬆️ something must happen before start something else Area: RBAC 🛂 Issues / PR's related to RBAC Type: Enhancement ✨ New feature or request and removed long-term labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: RBAC 🛂 Issues / PR's related to RBAC Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Enhancement ✨ New feature or request Type: Upstream Dependency ⬆️ something must happen before start something else
Development

No branches or pull requests

3 participants