Regression: cloudwatchevent_rule doesn't properly support JSON input_templates

[alalonde]

Summary

I reported this same bug over in the community.aws collection last year. It seems to have returned in this code.

Please see the previous issue report for a detailed reproduction example.

Issue Type

Bug Report

Component Name

cloudwatchevent_rule

Ansible Version

$ ansible --version

Collection Versions

$ ansible-galaxy collection list

AWS SDK versions

$ pip show boto boto3 botocore

Configuration

$ ansible-config dump --only-changed

OS / Environment

No response

Steps to Reproduce

Here is a working example using the AWS CLI:

eventbridge_target.json
{
   "Rule": "myRule",
   "Targets": [{
      ...
      "InputTransformer": {
         "InputPathsMap": {
            "s3Key": "$.detail.object.key"
         },
         "InputTemplate": "{\"containerOverrides\": [{\"name\": \"thrivSportsJob-stage_jobmg10\", \"environment\": [{\"name\": \"S3_KEY\",\"value\": <s3Key>}]}]}"
      }
   }]
}

Which can be executed with a aws events put-targets --cli-input-json file://eventbridge_target.json

However, when parsing the target configuration, the input is wrapped in a string:

                target_request['InputTransformer']['InputTemplate'] = '"{0}"'.format(
                    target['input_template']
                )

AWS will not route an event with an invalid transformer template. So the input for a JSON template must begin with a {, not a ". My solution was to remove the string wrapping, AND prepend the template with a space, as recommended here. This results in:

      -  name: Define trigger input template
         set_fact:
            trigger_input_template: |
               {
                  "containerOverrides": [{
                     "name": "{{container_name}}",
                     "environment": [{
                        "name": "S3_KEY",
                        "value": <s3Key>
                     }]
                  }]
               }
      -  name: Create rule in EventBridge
         community.aws.cloudwatchevent_rule:
            ...
            targets:
               -  id: "myJob-{{env}}"
                  ...
                  input_paths_map:
                     s3Key: "$.detail.object.key"
                  input_template: " {{trigger_input_template}}"
                  ...

Expected Results

I expected the input template to be wrapped by { ... } but was instead "{ ... }"

Actual Results

Code of Conduct

• I agree to follow the Ansible Code of Conduct