azurerm_automation_schedule - fix time in future validation #5876
Conversation
| @@ -82,7 +82,7 @@ func resourceArmAutomationSchedule() *schema.Resource { | |||
| Optional: true, | |||
| Computed: true, | |||
| DiffSuppressFunc: suppress.RFC3339Time, | |||
| ValidateFunc: validate.RFC3339DateInFutureBy(time.Duration(5) * time.Minute), | |||
| ValidateFunc: validate.RFC3339Time, | |||
There was a problem hiding this comment.
Since we are removing this constraint, could we add the constraint/check into the create/update function?
There was a problem hiding this comment.
Thanks for the suggestion. I have added the check into create/update function.
katbyte
changed the title
|
@katbyte Thanks for the suggestion. I have added the check into create/update function |
|
This has been released in version 2.1.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.1.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! |
ghost
locked and limited conversation to collaborators
fix #5726
terraform will always invoke validation function, we could not make terraform execute validation function only when field changes.
I think the best way for now to solve this problem is to remove the validation.