-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Added resource for SQL MI "azurerm_sql_managed_instance" #2727
Conversation
Hi @katbyte, @tombuildsstuff , did a rebase, and tests have passed successfully. 1) Timeout issue on create (6 hours): Is it possible to implement the Timeout on these resources? I didn't found this feature implemented at any other resource. |
wrt 1 - at the moment we don't have timeouts implemented, that is something we plan to implement for v2.0 so until then tested this will be.. difficult. We have a few ideas but none are idea (an ENV for a pre existing subnet where a MI has already been provisioned for example) |
There is a suggestion on #1747 that the creation time has been greatly reduced on the AzureRM side. Has anyone tested if this improves the situation sufficiently to make this provider usable? |
Is this feature planned to be merged any time soon? |
Any idea when this resource will be merged? Would love to see this available. Thanks! |
Will this resource be merged and released anytime soon? Received a time-out error running the code with ARM JSON. |
Would be awesome to see more progress on getting this pushed through! |
Any news on when this will be merged? |
I went to run these tests today and got the following build error (as we have updated the azure go sdk)
Went to merge master and push but it seems I can't? any chance you could update this se we could see if the instance provisions any faster now |
hi @kim0, the new PR is #3575 as this one seems to have been abandoned. Currently it is blocked with:
so any help on how to resolve that would be fantastic as i am working on other things at the moment. |
Hi @katbyte, |
@joranm, I believe that is in the works for v2.0 of the provider |
If you could pull in the changes from the PR i opened and or grant us push access to this branch we can take it from here |
Indeed, it's better than it was (36h) but it still takes a while; chatting with the SQL Team a while back it turns out there's multiple conditions where the Create/Update call could take this long:
As @katbyte has mentioned this is something we're doing as a part of the 2.0 release - at this point in time we're working on the dependencies to make that possible (we're working on switching out the Azure Storage SDK at the moment) at which point we should be able to enable Timeout support. However since this requires the Timeout support/this is going to ship in the 2.0 timeframe - I'm going to add this to the 2.0 milestone. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Optional: true, | ||
Default: 8, | ||
ValidateFunc: validate.IntInSlice([]int{ | ||
8, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few weeks ago a smaller number of vcores (4) was introduced:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-resource-limits#instance-level-resource-limits
It seems worthwhile to have this new resource up to date.
This has been released in version 2.0.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.0.0"
}
# ... other configuration ... |
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
New resource provider for SQL Managed Instance
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance
Known issues
Fixes #1747