Organization-wide environment variables.
complete
J
Jason
There are whole categories of env vars that should be shared across an organization. (Like API keys or credentials for package hosting services like gemfury.)
The Contexts feature is nice but unhelpful for jobs that aren't using workflows.
Related... why does the Import Env Var feature require admin privileges? If I have access to _add_ an env var, and I have access to the env vars of other projects, then by definition I should have access to import an env var from another project (to which I have env var access) into another project (to which I also have env var access).
CCI-I-467
Kate Catlin
complete
Hi Jason,
Is this still an issue for you?
We don't see anything in the new UI permissions for Import Env Vars that checks for admin. We believe this issue is specific to the old UI world.
Furthermore, as workflows/pipelines are now rolled out to all, all jobs have workflows. So Contexts should work for you as a universally shareable Env Var.
Thanks for your feedback, and let us know if we've closed this issue errantly.
Best,
Kate Catlin
Senior Product Manager, CircleCI