-
Notifications
You must be signed in to change notification settings - Fork 155
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
fix: Step function enrichment #149
fix: Step function enrichment #149
Conversation
* add variable to allow only pipe role creation
@antonbabenko could you have a look, please |
@@ -33,7 +33,7 @@ locals { | |||
matching_services = ["lambda"] | |||
}, | |||
step_functions = { | |||
values = [v.target, try(aws_cloudwatch_event_api_destination.this[v.enrichment].arn, null)], | |||
values = [v.target, try(v.enrichment, null)], |
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.
Why do you change this?
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.
because the matching service is states
and that can never be fulfilled by an api destination.
Co-authored-by: Anton Babenko <anton@antonbabenko.com>
## [3.14.3](v3.14.2...v3.14.3) (2025-01-28) ### Bug Fixes * Step function enrichment ([#149](#149)) ([8e1c345](8e1c345))
This PR is included in version 3.14.3 🎉 |
Description
Motivation and Context
The new variable allows to create the iam role only for pipe, for the cases where nothing else is created besides pipes, as for now you would end up with an additional role which is not needed
Breaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request