bug: CodePipeline not working with tag annotation

[lvthillo]

📜 Description

The CodePipeline plugin would work based on tag annotation, while CodePipeline tags are not propagated to AWS Config, which could be the reason why this is not working.

👍 Expected behavior

The plugin should work with the aws.amazon.com/aws-codepipeline-tags annotation.

AWS Config should support CodePipeline tags to make this plugin work.

Related: cloud-custodian/cloud-custodian#6204 (comment)

👎 Actual Behavior with Screenshots

The plugin works with the aws.amazon.com/aws-codepipeline-arn annotation but not with the aws.amazon.com/aws-codepipeline-tags annotation.

When using the tag annotation; the pipeline isn't shown.

👟 Reproduction steps

Use the aws.amazon.com/aws-codepipeline-tags in your catalog file.

📃 Content

Create a CodePipeline with tags in AWS; verify that the tags are not propagated to AWS Config.

🖥️ Your Environment

No response

[niallthomson]

Hi @lvthillo I exclusively use the tag-based lookup for CodePipeline so it is working, this does seem to be entirely related to the Config tag propagation.

We might have to introduce a way to source from multiple difference resource locators so it could fall back to resource tagging API where necessary.