CodePipeline onStateChange for Actions generates wrong detail-type

[PeterBengtson]

• I'm submitting a ...

  • 🪲 bug report

• What is the current behavior?

Create a CodePipeline with stages and actions. Set up on_state_change handlers for all three levels, like this (code is in Python, but I believe the situation is the same for all supported languages):

        my_pipeline.on_state_change(
            'MyPipelineStateChanges',
            target=events_targets.SnsTopic(internal_sns_topic)
        )

        my_stage.on_state_change(
            'MyStageStateChanges',
            target=events_targets.SnsTopic(internal_sns_topic)
        )

        my_action.on_state_change(
            'MyActionStateChanges',
            target=events_targets.SnsTopic(internal_sns_topic)
        )

This will set up three CloudWatch Event Rules.

• What is the expected behavior (or behavior of feature suggested)?

The three Event Rules should have different detail-type fields:

• The Pipeline rule should have "CodePipeline Pipeline Execution State Change"
• The Stage rule should have "CodePipeline Stage Execution State Change"
• The Action rule should have "CodePipeline Action Execution State Change"

However, the Action rule gets "CodePipeline Stage Execution State Change" and thus never will trigger, given that there also are conditions for the action's action name to match. This means that it's impossible to define on_state_change events for pipeline Actions in AWS-CDK 1.3.0.