Today, we’re officially releasing our new Contexts REST API.
With the new REST API, teams can securely rotate secrets automatically and atomically, which is especially useful if you have a lot of repositories, projects, and pipelines to manage. This new REST API was designed to save you time while enhancing your security practices.
For more details on how to begin automating your key rotation, check out our Contexts REST API documentation. If you have any questions, please contact our support team or leave a reply below.
Really excited to use this API endpoint, but there doesn’t seem to be a documented way to add security groups?
Seems like an issue in the UI as well since contexts are created with all members having access until you add the security groups in another step.
Welcome to Discuss @fbbct and great question!
At the moment there isn’t a way to set the restrictions via the API, and you are correct that it can only be done in the UI after the creation of the context.
I will note that when you first create a context there will not be any associated variables, so from a security standpoint not allowing the restrictions at creation shouldn’t be a concern. However, I do know it’s not ideal, especially if you are trying to automate setups.
With that in mind I have added a feature request:
I would recommend adding yourself as a ‘vote’ as you’ll then be automatically notified of any updates from the Product team. I hope that helps clarify and let us know if you need anything else!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.