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