Orbs

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.

Right now, CircleCI has released support for OIDC at the job-level: https://circleci.com/changelog/#oidc-tokens-in-jobs However, existing AWS or GCP Orbs do not currently support OIDC tokens. Customers can still use OIDC tokens to generate short-lived credentials, and operate with their AWS or GCP services through this without the Orbs However, for convenience of the customer, it would be great if our AWS or GCP Orbs are updated to extend support for customers wanting to use OIDC.

As I was creating my first Orb, I think it is useful to reuse executors when defining a job. For example my Orb have one Elixir docker image and a Postgres docker image. But if the project uses FakeS3 for testing, it will need to add another docker image.The current solution is to define a new executor that have all the docker images necessary. In the CircleCI docs there is an example of override executors ( https://circleci.com/docs/2.0/reusing-config/#overriding-keys-when-invoking-an-executor ) but the functionality I want is to allow to use the orb executor plus some others. CCI-I-895

Within our company, we are trying to migrate 100+ repositories to use CircleCI. In each repository, the config.yml is very similar, with only a few parameters different. Orbs would be greatly simplify our migration process, as it would remove duplication as well as enabling bugs to be fixed in a single place. CCI-I-960