Codecatalyst workflow manual approval action

4

One thing I can see people being interested in if they start to look at something like the examples posted where you can deploy to dev and then prod in the same workflows, is some option where you could look for a manual approval before moving from dev to prod.

Working with Enterprises, I often see these steps in other pipeline tools so that people involved in change management can approve changes before they're deployed to live.

And that leads onto a possible new role for colleagues in spaces/projects as an 'approver' ?

profile picture
asked a year ago586 views
4 Answers
1

+1 can we please get an update as to when this will be available?

this is definitely a show stopper for migrating to & productionalizing this product as currently we heavily depend on the APPROVAL STEP in AWS CodePipeline to block / hold and coordinate deployment into higher environments.

jacob
answered 8 months ago
  • This feature is currently on the roadmap to release in Q1 2024. Keep an eye on "What's New with AWS?" (https://aws.amazon.com/new) for feature announcements and updates.

0

Thank you for the feedback. Adding the ability to pause a workflow run to get manual approval to continue or reject the run is high on our roadmap. Is your expectation that the approvers are not set as part of the workflow configuration itself, but are defined elsewhere? And do you expect the approvers to be the same for any workflow in the project?

profile pictureAWS
EXPERT
Ranjith
answered a year ago
  • Hi, we are using CodeCatalyst and also interested in having this feature. For the approvers, I think it's fine if we can have a configuration section to set them within the space or project as Simon mentioned below. How's the progress for this feature release since I saw the question is asked 5 months ago :D

0

Hi Ranjith, personally I'd hope that the approvers were set as roles within the space or project, similar to a space/project administrator or contributor.

For myself, the ideal functionality would be that you could set approvers at either the space or project level using the roles mentioned, then within the workflow action you might be able to specify mandatory or optional approvers from the list, or at a minimum be able to set a minimum required number of approvers.

Note that approvers in this sense are different to PR-approvers, as they wouldn't necessarily be interested in looking at the code, but more around test coverage/results, tickets associated with the project, or external documents i.e. a change management team.

profile picture
answered a year ago
0

Hi, any issue tracker where we can track the feature release ?

answered 4 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions