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

data-factory forces replacement due to name change even with no changes #12099

Closed
calebak404 opened this issue Jun 7, 2021 · 2 comments · Fixed by #12128
Closed

data-factory forces replacement due to name change even with no changes #12099

calebak404 opened this issue Jun 7, 2021 · 2 comments · Fixed by #12128
Milestone

Comments

@calebak404
Copy link

calebak404 commented Jun 7, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

terraform 13.7
azurerm => 2.61

Affected Resource(s)

  • azurerm_data_factory

Expected Behaviour

Plan should have not suggested any changes.

Actual Behaviour

Plan suggests data factory name has changed from datafactory to DATAFACTORY

Steps to Reproduce

  1. deploy a data_factory resource with terraform using the name DATAFACTORY
  2. run terraform plan a second time with no changes
  3. terraform will want to change the name from datafactory to DATAFACTORY

Important Factoids

Resource name is all uppercase in the Azure Portal and inside the terraform state.
this issue was introduced in provider version 2.61, if we roll back to before 2.61 we do not have this issue

References

  • #0000
@github-actions
Copy link

This functionality has been released in v2.65.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@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 Jul 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants