Skip to content
New issue

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

Wrong Casing in Import Example providers/hashicorp/azurerm/latest/docs/resources/cdn_frontdoor_firewall_policy #19678

Closed
1 task done
dligthart opened this issue Dec 14, 2022 · 3 comments

Comments

@dligthart
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

Wrong casing in import documentation:

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cdn_frontdoor_firewall_policy

terraform import azurerm_cdn_frontdoor_firewall_policy.example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/resourceGroup1/providers/Microsoft.Network/frontdoorWebApplicationFirewallPolicies/firewallPolicy1
should be

terraform import azurerm_cdn_frontdoor_firewall_policy.example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/resourceGroup1/providers/Microsoft.Network/frontDoorWebApplicationFirewallPolicies/firewallPolicy1

Terraform Version

1.1.0

AzureRM Provider Version

3.35.0

Affected Resource(s)/Data Source(s)

azurerm_cdn_frontdoor_firewall_policy

Terraform Configuration Files

not applicable

Debug Output/Panic Output

ID was missing the `frontDoorWebApplicationFirewallPolicies` element

Expected Behaviour

Import successful!

The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.

Actual Behaviour

ID was missing the frontDoorWebApplicationFirewallPolicies element

Steps to Reproduce

Run terraform import according to documentation

Important Factoids

no

References

No response

@myc2h6o
Copy link
Contributor

myc2h6o commented Jan 13, 2023

@WodansSon
Copy link
Collaborator

I am going to close this issue since this was fixed in the linked PR.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants