Feature Requests

Currently, there is no out-of-the-box way to ensure that machine-provisioned EC2 instances can reach their own tags. The option is disabled by default and requires an API call to enable it. It would be great to have an option to enable it in CircleCI

Ability for CircleCI to run Windows with arm support.

We'd like to be able to efficiently ETL data out of CircleCI into our data warehouse so we're able to perform joins to other data sources and advanced analytics. In order to facilitate this process, we're using Fivetran. However, Fivetran makes over a million API requests to pull data which takes a significant amount of time. In order to facilitate incremental syncs, we'd like to see API endpoints provide filtering on "updated_at" and "created_at" attributes

As per https://github.com/circleci/circleci-docs/issues/2040#issuecomment-368139737 It would be nice for users to have a way to shallow clone. Currently, we do checkout to checkout. It would be nice to be able to pass a depth into that like shallowClone:10 and then use the number 10 as the depth for the clone. The PR linked has a modified version of the existing script that works. CCI-I-254

it would be nice if CircleCI supported an OpenTelemetry integration by out of the box.

Currently, email notifications can be configured for either "All Builds in My Projects", "My Branches" or "None". It would be very useful to have an option to receive email notifications only for builds I'm the author of, i.e. "My Commits" rather than "My Branches".

Currently when creating a scheduled pipeline trigger, intended to run once per hour, there is no control as to when the trigger will execute within the hour specified. In extreme cases it can run close enough to the end of the hourly window to cause confusion or delays relative to expectations. Per docs: "Why did my scheduled pipeline run later than expected?" https://circleci.com/docs/scheduled-pipelines/#scheduled-pipeline-run-later Although subsequent runs occur at a consistent time, greater control in specifying that recurring time is desired. Eg) a narrower 30 minute or even 15 minute time range would be desireable

Create some plugin with Grafana to send there metrics with some insights like build time

CircleCI Terraform provider would be great addition as it would allow to manage CircleCI projects using code. CCI-I-374

We have a ton of projects which use CircleCI and one bad actor can easily use up our concurrency limit and cause queuing across our entire org. It would be great if we could configure per-project specific concurrency limits so we can have finer grain control and limit the impact any one project could have on others.