AWS Role Assumption
grebols wrote: It would be nice to be able to replace the hardcoded and long lived AWS credentials you’re currently offering for access AWS APIs with the ability to assume a cross-account role with STS? for an example how datadog did it: https://docs.datadoghq.com/integrations/amazon_web_services/#installation CCI-I-709
Limit SSH Access To Admins
Enable a setting to restrict the "Rebuild with SSH" action to only administrators (role on Github Team) CCI-I-823
Ability to specify which environment variables are masked by Secret Masking
In some cases environment variables are useful to print out, it would be helpful to be able to whitelist the ones we'd like to show. CCI-I-1223
Make continue-config editable in UI
Feedback from customer: "This is a small niggle, but it's one that makes monorepo support feel like a bit of an afterthought: any view that shows you the config file (ie clicking Edit Config) is only aware of the main config.yaml, even though with this setup all of the important workflow config is in the separate chhild-config.yaml."
Enable manually triggering a pipeline that uses path-filtering orb
Feedback from customer: "Although I can manually run the pipeline, the child pipelines are dependent on the variables set by the path-filtering job so there is no way to manually run a pipeline for a particular service."
Allow deny-listing of domains or URL patterns
It would be nice to have a feature that allows cloud customers to prevent jobs from accessing certain domains or URLs that match a given pattern. Alternatively, we could prevent jobs from accessing any domain or URL that doesn't match an allowed pattern -- this may be a smaller list as the piplines may only need to access GitHub repos and known image repos.
Allow github app user access to restricted context
Similar to the question posted here: https://discuss.circleci.com/t/add-a-github-app-user-to-a-restricted-context/34775 We are currently using a github app to handle a merge queue for some of our repos and once the bot performs the merge the CircleCI workflow isn't able to perform the changes we need applied since it's unable to be a part of the restricted context. This is a huge blocker for us as we don't want to remove these restrictions as the post above suggests, allowing anyone in our org to make production changes.
attach a note for the job
It would be great if we have a option to attach a note for a circle ci job, so that we can reference later on what went wrong in that test
Break Plan Usage > Storage details down per project
As a CircleCI user, I want to see the Storage information on the Plan Usage page broken down per project, so that I can identify which project consumes most/least storage