Orbs

We would like to identify the version of the orb that a job is using, and pass that to our API. I do not see a corresponding env var in the current list . Could we get a new env var to get the version of the orb currently used?

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.

If I'm not mistaken, the "Usage" column for private orbs is not valuable in the UI. Since "private" orbs are private to the org, can't be shared to other orgs, and the usage column only indicates the usage in orgs, all private orbs would always show 1? It might make more sense to suggest "N/A", with a tool tip to this affect. Even better, would be data about how many projects in an org are USING a private orb.

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

When deploying an orb, the default should be Private. This currently defaults to public and requires a --private flag for the orb to then be Public.

Team, I did reach out to circle ci customer support for configuring slack notification on workflow fail/ pass. But after trying multiple solutions provided by Josh and team, we failed to achieve it. So please provide this feature. Requirement: Slack notification on workflow fail/ pass event Use case: Regression has multiple job setup to execute automation test cases in 5 containers. So once this jobs are completed I would like to receive a notification each job status in one line expected output: workflow master-regression failed Jobs: goals2019 - failed, rtf email_rtf- passed, profile- failed

In a single-file orb a developer can define some top-level parameters as yaml anchors and re-use them within different steps/jobs/workflows. This is a very handy tool for keeping the config file DRY. However, this feature does not appear to be supported when using the orb development kit. I propose that anchors should be able to be defined in the @orb.yml alongside other top-level config values. Example @orb.yml: version: 2.1 description: > Example for CircleCI orbs: aws-s3: circleci/aws-s3@2.1 awesome_param: &awesome_param description: >- Set to true if awesome. type: boolean default: true

.NET SDK 7 is now in the standard channel, and it would be immensely useful to have it installed in the Windows orb.

Status badges are only available for public orbs at the moment. Similar to the API token used for pipeline status badges, can we get this functionality for private orbs

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