fix(r/trigger): updating env-wide trigger causes apply error #709
Conversation
This file contains hidden or 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
jharley
commented
Jun 27, 2025
| state.ID = types.StringValue(trigger.ID) | ||
| state.Dataset = plan.Dataset |
There was a problem hiding this comment.
this is the bugfix
cewkrupa
approved these changes
Jun 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updating an env-wide trigger was not handling the
datasetattribute correctly resulting in an apply-time error.Also noticed that Trigger's didn't get the same update as SLOs to support importing environment-wide triggers by 'bare ID' (e.g. no need to use
__all__), so fixed that here and updated the test.