Orbs | CircleCI Ideas

Submit a Feature Request

For orbs-related bugs/issues, please submit them on the respective repo here: https://github.com/CircleCI-Public. For general feedback please use continue using this form.

Allow non-Owners to publish Orbs (aka granular permissions for orb publishing)

Could be a project level API key with publishing permissions, or use team membership like contexts do. Some means to expand the population of folks who can deploy prod versions of orbs without giving them global admin rights in GH. CCI-I-1108

Workflows in orbs

I want to be able to define an entire workflow in an orb, using the jobs of my orb and allowing parameters to conditionally choose which jobs to run and allow parameterization of branch and tag filters as well. CCI-I-615

Allow semantic ranges for orb versions

I'd like to be able to use an orb based on a semantic range, like you might do with npm dependencies. For example, this: orbs: some-orb: random-company/some-orb@^1.2.0 would resolve to the newest version at or above 1.2, but under 2.0. CCI-I-1078

Update .net windows orb to .net 6

.net sdk 6 is now in the LTS channel, and it would be imensly useful to have it installed in the windows orb. It seems that visual Studio 2019 is installed on that orb too. 2022 would be the current version of that.

Update .net windows orb to .net 6

Public to private Orb

Hey all, Is there any means to turn our public orb to private orb please ?

Allow referencing a Private Orb from within another Private Orb

Referencing public orbs from within other orbs is already possible. This is a request to extend that feature to Private Orbs, so that one private orb can be referenced from anther.

Windows Support for Slack Orb

Currently the Slack orb supports Linux x86_64, MacOS, and Arm64 V8. Presently it does not officially support Windows. This is a feature request to support Windows in the Slack Orb.

Allow CircleCI CLI commands to work with private Orbs

in progress

At the moment commands like orb source and orb info don't work with private Orbs as they are not available via the public registry. However, these commands are useful for maintaining and developing Orbs so they should be adde for private Orbs as well.

Allow Private Orbs along with Certified Public Orbs

under review

We are on Scale Plan and when I try to create a private orb, it requires me to toggle on "Allow all members of my organization to publish dev orbs, use uncertified orbs and use third-party ..". in the organization settings. However, in our scenario, we only want to allow private orbs along with certified public orbs. Please add a third option apart from the existing binary options: Yes: Allow all members of my organization to publish dev orbs, use uncertified orbs and use third-party .. No: Only allow my organization to use orbs certified and supported by CircleCI

→