Azure / Azure/bicep-types-az

Provider does not autoregister

Open
#2,268 0 comments 1 reaction 0 assignees View on GitHub
Needs: Triage :mag:
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

**Bicep version**
Bicep CLI version 0.29.47 (132ade51bc)

**Describe the bug**
While deploying my bicep project to a fresh subscription:
{"code":"SubscriptionIsNotRegistered","message":"Subscripton 'zzzzzzz-yyyy-yyyy-yyyy-xxxxxxxxxxx' is not registered with the required resource providers, please register with the resource providers Microsoft.App and Microsoft.ContainerService."}

**To Reproduce**
Steps to reproduce the behavior:

This is the resource that fails.
```bicep
resource container_app_env 'Microsoft.App/managedEnvironments@2023-05-01' = {
name: '${env_prefix}-app-env'
location: location
properties: {
vnetConfiguration: {
internal: false
infrastructureSubnetId: container_app_subnet_id
}
}
}
```

Full bicep project can be supplied if necessary. (I should try to reproduce this with a small sample project, but I'm running out of subscriptions)

**Additional context**
The group I'm a member of is the owner of the subscription.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source files, tests, or entry points are named. Start by reducing the deployment to the provided Microsoft.App/managedEnvironments resource and reproduce it in a fresh subscription. Done means the required Microsoft.App and Microsoft.ContainerService providers are registered automatically, or the behavior and its expected handling are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.