[pipelines/codepipeline] improve existing Action interface

[rix0rrr]

Need to address the following:

• More flexible ordering among Actions (autoderive ordering via artifacts and other relative "before/after" constraints)
• Change ordering among Stages (necessary to insert stages later)
• Make it easier to create new Actions (current interface is rather cumbersome, around actionProperties()/bind()/bound()).

More abstract things to think about:

• Compound actions?
• Should actions and stages not have been constructs?
• It should be easy to add a CodeBuild project to a pipeline "in one go", while allowing max. customization

---

This is a 🚀 Feature Request

[pcolazurdo]

Facing an issue related with this when trying to add permissions to the Action Role.

I'd prefer to have an interface like 'addToRolePolicy' in the CodeBuild module than having to define the role from scratch and assigning it to the Action.

As the Role is not exposed directly I'm finding very hard to use the existing interfaces to modify this.

[skinny85]

Why do you need to add permissions to that Role @pcolazurdo ?

[pcolazurdo]

In my case, I need to use a Full Clone to use AWS Copilot CLI - The permission setup for this are documented here and here

[skinny85]

I feel like that's more of a matter of the CodeCommitSourceAction not having support for that option.

But thanks!

[pcolazurdo]

I've also created a FR for the CodeCommitSourceAction but that will only solve the CodeCommit permissions, it should not change the CodeBuild construct.

Additionally, in my use case, I also had to add a policy to let the CodeBuild Role to assume a Role created by AWS Copilot to let CodeBuild call a stack change (this is due to how Copilot works but I can see this happening with other tools/frameworks)

[rix0rrr]

This change is unlikely to be necessary anymore as we've changed strategies for #10872

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.