microsoftgraph / microsoftgraph/msgraph-bicep-types
Graph Bicep module does not work with deployment stack
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 80
- Forks
- 15
- Avg merge
- 1h 21m
- Merged PRs (30d)
- 3
Description
Bicep version
Bicep CLI version 0.44.1 (28275db947)
Resource and API version
Which Microsoft.Graph resource and API version has the issue?
- br:mcr.microsoft.com/bicep/extensions/microsoftgraph/v1.0:1.0.0
- Microsoft.Graph/servicePrincipals@v1.0
Auth flow
CD deployment in Azure Devops pipelines using the AzureCLI@2 task and a managed identity with the required Application.Read.All and AppRoleAssignment.ReadWrite.All permissions.
Deployment details
Please refer to #302
Describe the bug
When deploying the bicep mentioned in #302 using deployment stack, the error (also described in #302) is triggered.
To Reproduce
- Create a bicep deployment that deploys the bicep in #302.
- Have a managed identity that has the
Application.Read.AllandAppRoleAssignment.ReadWrite.AllGraph permissions. - Use that managed identity (e.g. in a CD pipeline in Azure DevOps) and run
az stack sub createto deploy it.
Additional context
It is quite a showstopper since it doesn't work with deployment stacks...
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.
Research direction
Start with the deployment details in issue #302 and reproduce the reported failure using the Graph servicePrincipals@v1.0 resource and az stack sub create with the stated managed identity permissions. Done means the Bicep deployment completes successfully through a deployment stack without triggering the error described in #302.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100