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.
This PR fixes a bug where setting
error_integration
on asnowflake_pipe
resource would cause the name of the integration to be written to the comment field on the pipe instead of the error integration. A separate bug prevented theerror_integration
diffs from being detected if an SNS topic was set.Test Plan
I tested this using an existing stack where I have many pipes. I made an earnest attempt to update
pipes_integration_test.go
, but I reached the point where I needed a real SNS topic and decided that was beyond the timebox I set for this.Using version 0.76.0:
comment
but noerror_integration
error_integration
to the terraform config.describe pipe
on the updated pipes in Snowflake. The comments now contained the name of the notification integration, whereaserror_integration
was null.describe pipe
on the updated pipes in Snowflake. The comments were back to their previous value, buterror_integration
was still null.error_integration
from the terraform config.describe pipe
on the updated pipes in Snowflake. The comments were now blank.Using the modified provider
comment
but noerror_integration
error_integration
to the terraform config.describe pipe
on the updated pipes in Snowflake. The comments were unchanged and error integrations were set to the expected value.error_integration
from the terraform configdescribe pipe
on the updated pipes in Snowflake. The comments were unchanged, and error integrations were null.References
I initially started to file a bug report, but during investigation I figured out how to fix it so I'm opening a PR instead. Let me know if this isn't the right process