azurerm_frontdoor - Fix timeout for read operation to match documentation
#7408
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
katbyte
added a commit
that referenced
this pull request
Jun 23, 2020
tombuildsstuff
added a commit
that referenced
this pull request
Jun 25, 2020
|
This has been released in version 2.16.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.16.0"
}
# ... other configuration ... |
jrauschenbusch
pushed a commit
to jrauschenbusch/terraform-provider-azurerm
that referenced
this pull request
Jun 29, 2020
…tation (hashicorp#7408) I have increased the timeout in the resource code from 5 minutes to 6 hours per the documentation. While this may seem excessive for a read, the time may be necessary for the frontdoor resource to complete successfully especially when custom domain SSL certs have been defined. (fixes hashicorp#7405)
jrauschenbusch
pushed a commit
to jrauschenbusch/terraform-provider-azurerm
that referenced
this pull request
Jun 29, 2020
jrauschenbusch
pushed a commit
to jrauschenbusch/terraform-provider-azurerm
that referenced
this pull request
Jun 29, 2020
…tation (hashicorp#7408) I have increased the timeout in the resource code from 5 minutes to 6 hours per the documentation. While this may seem excessive for a read, the time may be necessary for the frontdoor resource to complete successfully especially when custom domain SSL certs have been defined. (fixes hashicorp#7405)
jrauschenbusch
pushed a commit
to jrauschenbusch/terraform-provider-azurerm
that referenced
this pull request
Jun 29, 2020
jrauschenbusch
pushed a commit
to jrauschenbusch/terraform-provider-azurerm
that referenced
this pull request
Jun 29, 2020
|
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! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have increased the timeout in the resource code from 5 minutes to 6 hours per the documentation. While this may seem excessive for a read, the time may be necessary for the frontdoor resource to complete successfully especially when custom domain SSL certs have been defined.
(fixes #7405)