Add follow project endpoint to v2 API
The v1 API had an endpoint for following a new project https://circleci.com/docs/api/v1/#follow-a-new-project-on-circleci The v2 project endpoint currently does not have an equivalent config https://circleci.com/docs/api/v2/?section=reference#tag/Project Some users rely on this endpoint, and it would be helpful as the v1 endpoints will be depreciated
Allow more powerful template expressions in the config.yml file. For example, the << parameters.foo >> expression is just a simple string replacement. If we wanted to transform the value of the foo parameter to lowercase for example, it'd be nice to do something like << parameters.foo | tolower >> . More context can be found here: https://discuss.circleci.com/t/built-in-functions/39129
Project setup and configuration in API v2
For organizations with hundreds of GitHub repos, project creation tooling is essential, but currently, the tooling in our organization is not able to setup new repos in CircleCI using APIv2, since this API version simply does not expose this functionality. This is possible in APIv1.1, and it feels rather counter productive to remove this ability in the new API version.
Set Up New Project API
An API endpoint to start build a new repo with an already existing config. We have a terraform pipeline to manage Github repositories but we still need to manually add project to circleci.
Atomically Change Multiple Secrets
To prevent the possibility of mixing new and old credentials, it would be helpful to have the ability to change multiple secrets in a context atomically.
Endpoint to follow project using the CIrcleCI v2 API
Currently, you can follow a project using the CirlceCI v1 API. The CircleCI v2 API does not have a similar endpoint to follow a project.
API V2: Would like to know pipeline status
I would like to know the "pipeline status" through the new API V2. CCI-I-1391
Jobs / Workflows include a project API token that can be used to make API calls
This is similar to GitHub Action's GITHUB_TOKEN. Ideally, this token is auto-rotated by CircleCI so it doesn't go stale. CCI-I-1510
Public API to get the last successful build for a specified job
Sometimes I need to get the last successful build for a specified job. Currently I use the API to list builds and filter by jq like below. $ curl -s " https://circleci.com/api/v1.1/project/:vcs-type/:username/:project?circle-token=:token&limit=100&filter=successful " | jq -r '[. | select( .workflows.job_name == ":job_name" )] | max_by(.build_num).stop_time' But it's complicated and it becomes more difficult in the case that the last successful build for a specified job is not in recent 100 builds. So it will be helpful if there is a public API to get information of the last successful build for a specified job. FYI, Jenkins has an easy way to retrieve last successful build. https://stackoverflow.com/questions/31508603/how-to-retrieve-build-id-of-latest-successful-build-in-jenkins CCI-I-693
Populate trigger_parameters in pipeline response
The v2 API documentation shows trigger_parameters as a non-required property of the pipeline API call response. This property is never populated, and support has explained that it is only for internal use. But it would be extremely useful to see these parameters, if not in the UI then at least in the API response.