fix: Made input_paths in input_transformer optional #116
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.
Per AWS provider documentation,
input_paths
is not required.Fixes #117
Description
Per the AWS Provider documentation on aws_cloudwatch_event_target,
input_paths
is optional.Motivation and Context
Scenario:
You have a rule of type "Scehduled Standard" and a target of a Batch job queue. You wish to use an
input_transformer
of type "Constant" and supply some static JSON forinput_template
. This means you will not have any need forinput_paths
. Currently the module requiresinput_paths
to be set.Breaking Changes
Not that I am aware
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectsI use this module at my place of employment and have tested this change with our implementation of this module and confirmed the change requested here does not break usage of the module.
pre-commit run -a
on my pull request