https://circleci.com/docs/2.0/env-vars/ mentions using environment in (normal) job steps:
Whether I use key / value or an array + key value, this seems to fail validation, since environment isn’t a valid param of the orb:
version: 2.1 orbs: bar: foo/bar@1 workflows: version: 2 pipeline: jobs: - bar/deploy: context: org-global environment: - FOO: 'bar' target-env: blah
What’s the canonical way to allow setting env vars in an orb? Just having a passthrough parameter? Anyone have a good example of this? Alternately, I guess I could override environment for the executor instead?