I'd like to implement an integration with Terraform so Amazon access keys can automatically be maintained and updated in build contexts, see this issue: https://github.com/hashicorp/terraform/issues/17951
At our company we also have to add extra contexts because were are unable to add ENV variables through the API. Ideally the information we pass to terraform could then be passed into circle, instead, we need to manually add/modify contexts to run terraform commands. For companies like mine that really love IAC this would be a huge win.
+1 Figured that this would've already been supported.
+1 Definitely need this
+1 Context management for a large github org is painful. This would make it much less so.
Oh my goodness, +1
We use tokens inside our contexts to access external services. Would love to automate the secrets rotation within contexts as we have 100s of projects.
+1 This is absolutely required. We use dozen of variables for our microservices ECS cluster. We need to backup these values while scripting their deployment at the same time as we use to do in IaC.
Contexts are a wonderful thing, but not really useful or convenient to use without:
1. this API
2. the capability to see the content of some variables as they are not supposed to be secrets. It's mandatory to ease the readability during investigations.
+ 1 I need to store secret keys per context via API. Actually there's no way to do this
An absolute requirement for rotating secrets
Please ... this is a must have!
we'd like it as well
how is this not a thing?
Can we please get this
We definitely need a fully featured API for managing Context's, and that should include the ability to CRUD/clone and modify existing properties and their values within a Context.
The new contexts variables that are only available to administrators are wonderful. Unfortunately, we have an automated system that rotates our deployment API keys daily.
Without an API to manage contexts, we can't update the API keys, which means we'd have to have stagnant ones that we update manually. This is a security issue!
At Shelf we are using single context per project (repo) and since we are doing serverless it requires every time to the context manually from different sources which just takes time for a dummy work. Definitely needed!
+1 this would ease automation of secret creation in our org and really enhance security.
You won't be notified about changes to this idea.