question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hardcoded API version 2022-02-05 in @azure/arm-deviceprovisioningservices dpsClient cannot be overwritten and is not supported on "northeurope"

See original GitHub issue

Describe the bug

When using the DPS Client, all requests fail when using the region northeurope because the hardocded API version 2022-02-05 cannot be overwritten using the client options when constructing the client.

To Reproduce

const armIotDpsClient = new IotDpsClient(credentials, subscriptionId)
await armIotDpsClient.iotDpsResource.listKeys(dpsName, resourceGroupName)

Error:

{
  "error": {
    "code": "NoRegisteredProviderFound",
    "message": "No registered resource provider found for location 'northeurope' and API version '2022-02-05' for type 'ProvisioningServices'. The supported api-versions are '2017-08-21-preview, 2017-11-15, 2018-01-22, 2020-01-01, 2020-03-01, 2021-10-15'. The supported locations are 'westus, australiacentral2, australiasoutheast, canadaeast, centralus, eastus, francesouth, koreasouth, japanwest, southindia, southeastasia, westeurope, uksouth, southcentralus, australiacentral, australiaeast, brazilsouth, canadacentral, centralindia, eastasia, francecentral, japaneast, koreacentral, northeurope, ukwest, westus2, westcentralus, northcentralus, eastus2'."
  }
}

Expected behaviour

I expect to be able to use listKeys for DPS using the client in the region.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:14 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
coderbyheartcommented, Jun 2, 2022

Can confirm that the 5.0.1 version fixes it for me.

1reaction
qiaozhacommented, May 26, 2022

we will generate a new package that allows customers to change the api version in the client options. But it still needs service team’s attention for the version of 2022-02-05, as it has been merged into the rest api specs main branch https://github.com/Azure/azure-rest-api-specs/tree/main/specification/deviceprovisioningservices/resource-manager#basic-information but we can’t find this api version in service’s ARM manifest.

Read more comments on GitHub >

github_iconTop Results From Across the Web

[BUG] Cannot add DataAction roles · Issue #30374 · Azure ...
"Assignments to roles with DataActions and NotDataActions are not supported on API version '2015-07-01'. The minimum required API version ...
Read more >
Azure Migrate Rest API 2018-02-02 not supported
I am trying to automate the Migration grouping and assessment using available Azure Rest API 2018-02-02 , I don't know when new version...
Read more >
Ask Question
I am querying the data factories within a resource group but I couldn't make it work. I can query it through the rest...
Read more >
How to remediate sensitive data leaks such as API keys ...
How to remediate sensitive data leaks such as API keys hardcoded in ... then push the cleaned version back, or git push --force...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found