-
Notifications
You must be signed in to change notification settings - Fork 65
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
[Task] Refactor locks into new package to align with azurerm provider #110
Comments
Moved lock functions to locks package hashicorp#110
The locks package file is identical to the azurerm locks.go file. However, the azurerm locks package is internal. Ideally, both providers could use the same file. I will raise an issue in the azurerm repository.
|
Going to close this issue/PR for now. It seems there is the intention to add engineering effort on this teams to accelerate the development. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
The terraform-provider-azurerm provider has moved the resource locking functionality into separate package back in Aug 2019. Having the terraform-provider-azurerm provider diverge makes it more difficult to create new resources on Azure Stack (ie #50) that are derived from the Azure Cloud. If the model in the Azure Cloud has stabilized, I propose starting migrating to similar packages in Azure Stack.
See issue #109
The text was updated successfully, but these errors were encountered: