Orb-level parameters


#1

Are there ways to set a parameter that affects the behavior of the entire orb?

For example, let’s say I have 5 workflow steps that all override the cache-key with the same value. I would have to set that parameter on each of those, right?

Additionally, it might be nice to invoke an orb once with a top level param that influences the behavior of other commands. For example, a node orb, being able to set whether npm or yarn is the package manager might be a better way of influencing defaults (see, e.g., discussion in https://github.com/CircleCI-Public/circleci-orbs/pull/85)


#2

@wyardley This is good food for thought!

I know that the team is currently sketching out ideas for some kind of top-level concept of orb parameters—i.e., defining parameters for an entire orb, which would then filter down and/or influence the behavior of individual parameters in commands/jobs.

Good to know that we’re on the right track :slight_smile: