CircleCI Ideas

Allow restricted contexts within scheduled workflows

As of right now, scheduled workflows only work with contexts configured with an "all members" security group. If any other security group is associated with a context, workflows will fail with unauthorized status. It would be great if there were a mechanism to control the scope of a context used within a scheduled workflow. 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 4 2019
  • Taking votes
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    25 Jun 12:55pm

    +1

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Jun 08:34am

    Any update on this? It's more than 1 year...

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    16 May 10:30pm

    This is definitely needed in any non-trivial multi-environment build implementations.
    +1

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    8 May 06:29pm

    +1

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    4 Mar 05:59pm

    Plus 1

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    2 Mar 09:49pm

    +1

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    5 Feb 07:33pm

    very useful!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    6 Jan 05:22pm

    Not sure how to vote but +1

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    1 Aug, 2019 07:43am

    +1