Are there any update on this?

so, another year and nothing new regarding this feature?

Any update on this? This is a highly coveted feature.

"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!

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

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.

Thank you so much for your interest!

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

Thanks!

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

@Nathan any update on this?

@Kunal Do you have an update?