Closed MattDelac closed 9 months ago
Hey @MattDelac. Thanks for reporting the issue.
This error was fixed in #2287 (available in v0.81.0). There are some other problems with this resource solved with #2319; these will be released tomorrow as a part of v0.83.0.
Please bump to v0.81.0 or wait for v0.83.0 and bump then; this should solve your problem.
Hey @MattDelac. Thanks for reporting the issue.
This error was fixed in #2287 (available in v0.81.0). There are some other problems with this resource solved with #2319; these will be released tomorrow as a part of v0.83.0.
Please bump to v0.81.0 or wait for v0.83.0 and bump then; this should solve your problem.
That's great. I will wait for 0.83.0 then
Thanks
Terraform CLI and Provider Versions
Snowflake-Labs/snowflake = 0.73.0 Terraform v1.5.5
Terraform Configuration
Expected Behavior
terraform apply
should work when modifying partially the resourcesnowflake_resource_monitor
Actual Behavior
With the following piece of code
When I removed the "notify_users" parameters,
terraform plan
was good butterraform apply
crashedLogs
I had a similar behaviour when I only changed the start_timestamp even if the
frequency
parameter remains the sameSteps to Reproduce
resource snowflake_resource_monitor
blockstart_timestamp
while keeping the same value for thefrequency
user_notify
parameters (or put an empty list)terraform apply
How much impact is this issue causing?
High
Logs
No response
Additional Information
Impact is high as the only workaround is to destroy and create again the resources which is a real time sink