We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using Pulumi TypeScript, v1.3.4
Resource: Azure Maps Account azure.maps.Account
azure.maps.Account
There is a mismatch between the skuName returned by Azure and the skuName allowed by Pulumi - this is causing unnecessary updates to be performed.
Create a new azure maps resource:
const maps = new azure.maps.Account("maps", { resourceGroupName: rg.name, skuName: "s0", });
Run pulumi up - this should work, and the maps account should now exist.
pulumi up
Run pulumi up again, and the maps account will be updated:
azure:maps:Account maps replace [diff: ~skuName]
Drilling into the diff:
~ skuName: "S0" => "s0"
Attempting to fix the skuName results in the following error:
azure:maps/account:Account resource 'maps' has a problem: expected sku_name to be one of [s0 s1], got S0
The text was updated successfully, but these errors were encountered:
This might be an issue with the Terraform provider
https://www.terraform.io/docs/providers/azurerm/r/maps_account.html#sku_name
Sorry, something went wrong.
Let's track it upstream: hashicorp/terraform-provider-azurerm#4706
stack72
mikhailshilkov
No branches or pull requests
I'm using Pulumi TypeScript, v1.3.4
There is a mismatch between the skuName returned by Azure and the skuName allowed by Pulumi - this is causing unnecessary updates to be performed.
Steps to Reproduce:
Create a new azure maps resource:
Run
pulumi up
- this should work, and the maps account should now exist.Run
pulumi up
again, and the maps account will be updated:Drilling into the diff:
Attempting to fix the skuName results in the following error:
The text was updated successfully, but these errors were encountered: