Orbs

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.

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.

It would be nice to be able to reuse orbs by simply referencing the git repo and tag.

As a user who has projects spread across multiple organizations, it would be helpful if an org could be allowed to use a private orb from another org.

The Jira Orb ( https://circleci.com/orbs/registry/orb/circleci/jira ) notifies on git commits, but it appears GitHub releases are treated similar to tags therefore the Jira Orb can't notify on releases. It does look like the GitHub releases endpoint ( https://developer.github.com/v3/repos/releases/#response ) has a "body" field (description)

When using Lerna, there is a parameter which will assign a number of CPUs to use. It would be useful to have an orb that would lookup the number of CPUs for the defined resource class, and amend the Lerna command to that number

build

This is a request for an orb that allows deployment to Sharepoint / OneDrive for Business.

On the autogenerated page in the Orbs Registry for private orbs, it shows a "private" tag after the name of the orb. In the next line, there is metadata such as Created, Version Published, and Releases. This line also indicates that the orb issued in < 25 orgs. However, currently orbs can only be used by one (I believe). It would make sense to hide this field (number of orgs used) in the published documentation for any private orb as it's not pertinent.