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 the deletion of private orbs so users can stay within their orb limits. Private orbs have a limited scope of users, so if the owner is aware of the risks of breaking internal CI pipelines then they should have the option to delete orbs as necessary.

At the moment private Orbs are not appearing on the registry. However, it would be nice if anyone who had access to a private Orb (AKA anyone at the Organization that published it) could view it on the registry. This would likely require some sort of verification of access, maybe even having to log into CircleCI first to verify.

Currently "Allow Uncertified Orbs" of "Orb Security Settings" have binary option to allow to use third-party orbs or not.We wish to use WHITE LIST orb provider. CCI-I-687

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

The current limit on Orbs is three and once an Orbs is created it cannot be removed so there is currently a hard limit of three, so we would like to raise this limit.

A simple view in the UI that shows all of the orbs my orgniazaiton is using and what projects are using them.

It'd be useful to allow handling lists of values for a parameter, without having to resort to workarounds like parsing comma-separated lists in string types. I think it would be useful to be able to specify something like: steps: - myorb/foo: bar: - baz - qux And have the myorb/foo command called with a bar parameter equal to [ "baz", "qux" ] . CCI-I-701

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

Copied from: https://discuss.circleci.com/t/support-for-full-semver-2-0-0-specification/41111 I’d like to publish my orbs such that build metadata is included in the version (i.e. v1.0.0+aef234b.34). This is so that we can quickly work our way back to the commit (via the git short sha) and the build (via the circle ci build number) that produced the published orb. This is very helpful for us during times when we need to debug something. Are there plans to support the full SemVer 2.0 standard as specified here? https://semver.org/#backusnaur-form-grammar-for-valid-semver-versions