CircleCI Ideas

Specified persons only can approve the workflow

When we have a deploy job to production, we need only Managers to approve the workflow. Currently anybody following the project can approve the workflow. Better still can you trigger a email with the approval link?

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 3 2018
  • Shipped
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    24 Oct, 2019 05:10pm

    "Using restricted context, you can control who has access to credentials for all the downstream jobs. "

    It makes more sense to avoid the execution of the job instead of failing with unauthorized!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    29 Mar, 2019 08:49pm

    Using restricted context, you can control who has access to credentials for all the downstream jobs. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    18 Mar, 2019 06:57pm

    Sweet. My managers have been bugging me about this. We want to restrict who can deploy to prod but let everybody deploys to QA/staging. We have different contexts with same keys for credentials. This will let us control who can trigger job with credentials for productions.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    18 Mar, 2019 06:30pm

    Thank you so much for your interest! 

    We are in process of rolling out `restricted contexts` feature that will help with this particular use case. Please free to review the docs PR if you are interested. 

    Thanks!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    14 Mar, 2019 06:03pm

    @Kunal @Nathan
    Any additional information or update on the status of this feature?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    8 Feb, 2019 05:07pm

    @Nathan any update on this?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    24 Jan, 2019 08:28pm

    @Kunal Do you have an update?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    28 Aug, 2018 10:44pm

    We are currently testing this feature internally. I will update this thread when we are ready to roll it out. Thank you so much for your patience.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    28 Aug, 2018 08:34pm

    We can't use CD on CircleCI until something like this is implemented. Restricting to users named in the contect or an option to restrict approval to github repo admins would either be OK. But we have new developers and we have consultants who have write access to the repo, so we need to be able to have production deploy trigger restricted.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    22 Aug, 2018 07:57pm

    The holds feature is nice. I don't think we have a use case as is. If we can limit who can approve the holds we will start using it as soon as it is available.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    10 Aug, 2018 07:41pm

    I am also looking forwards to this feature. We want to allow only a group of user to approve a job in workflow before the next job of deploying to production.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Jun, 2018 10:22am

    Any news about this feature ?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    7 Jun, 2018 01:18am

    That is good enough for our use case, thanks for the info, and looking forward to it.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    6 Jun, 2018 06:26pm

    The first feature that will allow something like this will be the ability to protect contexts to be executed only by certain people in a group -- this will locate the restriction on the downstream job rather than the approval itself, however, so we may also provide approval-level restrictions later.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    6 Jun, 2018 02:05pm

    @Nathan can you share any update on this? if any

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    3 Apr, 2018 08:06pm

    We have something along these lines in the works. Stay tuned...