API

At the moment, context restrictions can only be set via the UI once a context has been created. To allow for more programmatic creation of contexts, allow for the ability to set restrictions either at creation or after the context has been created, via the API.

I'm using this but when I consume this service " https://circleci.com/api/v2/project/{project-slug}/pipeline " it execute two workflows at time What parameter can I use to select specific workflow? #------------------------------------------ JOB EXECUTION API ------------------------------------------------------# report-test-vpn: jobs: - build_and_test_vpn: platform: << pipeline.parameters.platform_workflow >> context: << pipeline.parameters.context_workflow >> execution-tags: << pipeline.parameters.tags_external_workflow_only_execution >> notification-information: << pipeline.parameters.text_notification_slack_external_workflow >> slackChannel1: << pipeline.parameters.channel _1_slack_external_workflow >> slackChannel2: << pipeline.parameters.channel _2_slack_external_workflow >> filters: branches: only: << pipeline.parameters.branch_execution >> #------------------------------------------ JOB EXECUTION API sin VPN------------------------------------------------------# report-not-vpn: jobs: - job_only_one_execution: environment: << pipeline.parameters.environment_external_workflow >> platform: << pipeline.parameters.platform_workflow >> tags: << pipeline.parameters.tags_external_workflow_only_execution >> context: << pipeline.parameters.context_external_workflow >> filters: branches: only: << pipeline.parameters.branch_execution >> - send_notification_slack_only_execution: environment: << pipeline.parameters.environment_external_workflow >> platform: << pipeline.parameters.platform_external_workflow >> notification-information: << pipeline.parameters.text_notification_slack_external_workflow >> slackChannel1: << pipeline.parameters.channel _1_slack_external_workflow >> slackChannel2: << pipeline.parameters.channel _2_slack_external_workflow >>

Ability to manage the security group membership for contexts via API: https://circleci.com/docs/contexts/#restrict-a-context-to-a-security-group-or-groups Currently this appears to be accessible only via the web UI.

CircleCI's web UI is exposing last 4 digits of the value in environment variables of contexts, however, the equivalent information isn't available via https://circleci.com/docs/api/v2/index.html#operation/listEnvironmentVariablesFromContext Unlike contexts's environment variables, API for project-level environment variables are displaying last 4 digits of those sensitive values for help inspecting (cf. https://circleci.com/docs/api/v2/index.html#operation/listEnvVars ). It's nice if contexts API also behaves similar way.

It would be nice to be able to add Security to a Context via the CircleCI CLI or API vs. currently, where its only available in the UI. This was confirmed via CIrcleCI support.

Would it be possible to add support for contexts using the old build api: https://circleci.com/api/v1.1/project/:vcs-type/:username/:project/tree/:branch?circle-token=:token My use case is as following: I've a deploy which is manually invoked through the api. Each deploy has some different set of parameters hence I must use the old api (since I require the use of build_parameters). I would like to store env vars in contexts instead of sending them via the build parameters since it is more organized this way (I would just invoke the api and tell it which context name to use). Also, I'm using the old api since it supports specifying the config file as a parameters which is very convenient when testing CCI-I-1088

We currently return created_at, but not updated_at. The latter is a much more useful piece of data to return since it pertains to secret rotation/changes. It would be ideal to return both of these values in env var data, e.g. https://circleci.com/docs/api/v2/#operation/listEnvironmentVariablesFromContext We already have this data in our DB; it's just a matter of including it in internal and public API responses.