-
Notifications
You must be signed in to change notification settings - Fork 418
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
Altering Resource Monitors doesnt work as expected #1832
Comments
Hey 👋 |
## Changes - Add ValuePresent assert to our custom assertions - Add ToConfigValues function for every model - Update Resource Monitor SDK + unit and integration tests - Update Resource Monitor Resource + acc tests - Handle issues connected to the resource monitor (mostly timestamp format difference causing infinite plan or only trigger updates causing SQL compilation error): - #1500 - #1624 - #1716 - #1754 - #1821 - #1832 - #1990 ## Next pr - Adjust examples and update migration notes - Data source (impl, tests, examples, migration notes) ## References * [CREATE RESOURCE MONITOR](https://docs.snowflake.com/en/sql-reference/sql/create-resource-monitor)
## Changes - Add ValuePresent assert to our custom assertions - Add ToConfigValues function for every model - Update Resource Monitor SDK + unit and integration tests - Update Resource Monitor Resource + acc tests - Handle issues connected to the resource monitor (mostly timestamp format difference causing infinite plan or only trigger updates causing SQL compilation error): - #1500 - #1624 - #1716 - #1754 - #1821 - #1832 - #1990 ## Next pr - Adjust examples and update migration notes - Data source (impl, tests, examples, migration notes) ## References * [CREATE RESOURCE MONITOR](https://docs.snowflake.com/en/sql-reference/sql/create-resource-monitor)
Hey 👋 |
Closing due to long inactivity. Please, create another issue if you think the problem is still not resolved. |
Provider Version
The provider version you are using.
0.55.1
Terraform Version
The version of Terraform you were using when the bug was encountered.
1.0.11
Describe the bug
Changing only the triggers of a resource monitor throws a syntax error
For example take the following monitor:
If I were to say change a trigger line to
notify_triggers = [95]
and change nothing else then the provider produces the following SQL:This fails with
Expected behavior
A clear and concise description of what you expected to happen.
Based on the docs you must put something (not triggers or notify users) in the SET clause. The following SQL will work:
edit: The following will also work
I would expect the provider to produce this SQL
Code samples and commands
Code samples are in the description already
Additional context
I assume the same issue exists for changing only the notify users but have not tested this.
The text was updated successfully, but these errors were encountered: