-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Support conditions in action triggers #37485
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
Conversation
917b227 to
768e723
Compare
7d8d086 to
d510795
Compare
ab10206 to
ae9ee37
Compare
liamcervante
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just minor nits
57fbdb1 to
154b9ce
Compare
liamcervante
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry - unbelievable minor nits
fa83a1a to
d4a23cb
Compare
we don't really care about the expansion in this context
Co-authored-by: Liam Cervante <liam.cervante@hashicorp.com>
d4a23cb to
254c057
Compare
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
This PR adds basic support for conditions in lifecycle action_trigger blocks. Conditions can only contain
count.index,each.key,each.value, andselfif the action_trigger events list does not contain abefore_*action since we don't know the values for these things at that point in time.Target Release
1.14.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry