Azure / Azure/bicep-types-az

[Microsoft.ApiManagement/service@2024-05-01]: fails to deploy to Azure

Open
#2,301 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

inaccuracy
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

Resource Type

Microsoft.ApiManagement/service

Api Version

2024-05-01

Issue Type

Resource fails to deploy

Other Notes

I'm getting the following error when trying to deploy API Management with version 2024-05-01 (types.md).

No registered resource provider found for location 'westeurope' and API version '2024-05-01' for type 'service'. The supported api-versions are '2014-02-14, 2015-09-15, 2016-07-07, 2016-10-10, 2017-03-01, 2018-01-01, 2018-06-01-preview, 2019-01-01, 2019-12-01-preview, 2019-12-01, 2020-06-01-preview, 2020-12-01, 2021-01-01-preview, 2021-04-01-preview, 2021-08-01, 2021-12-01-preview, 2022-04-01-preview, 2022-08-01, 2022-09-01-preview, 2023-03-01-preview, 2023-05-01-preview, 2023-09-01-preview'. The supported locations are 'centralindia, uaenorth, australiacentral, germanywestcentral, westcentralus, norwayeast, switzerlandnorth, koreasouth, westindia, koreacentral, southafricanorth, ukwest, brazilsouth, eastasia, southindia, canadacentral, canadaeast, australiasoutheast, japaneast, northcentralus, southeastasia, westus2, centralus, uksouth, australiaeast, japanwest, westus, francecentral, southcentralus, eastus2, eastus, northeurope, westeurope, westus3, jioindiacentral, jioindiawest, swedencentral, qatarcentral, polandcentral, italynorth, spaincentral, mexicocentral, israelcentral'.

This version is also not documented on https://learn.microsoft.com/en-us/azure/templates/microsoft.apimanagement/service?pivots=deployment-language-bicep.

Bicep Repro

No response

Confirm
  • I have read the troubleshooting guide and looked for duplicates.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with generated/apimanagement/microsoft.apimanagement/2024-05-01/types.md and compare the listed API version with Azure's supported versions and the linked Microsoft documentation. A deployment repro is missing, so first verify whether the version is valid for westeurope; done means the type definition and documentation accurately reflect the provider's support.

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
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.