Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage secrets with ESC #1207

Open
blampe opened this issue Dec 10, 2024 · 0 comments
Open

Manage secrets with ESC #1207

blampe opened this issue Dec 10, 2024 · 0 comments
Labels
kind/enhancement Improvements or new features

Comments

@blampe
Copy link
Contributor

blampe commented Dec 10, 2024

CI workflows often consume over a dozen secrets via environment variables -- some of which were set years ago and aren't available in 1pass. This makes it very difficult (and sometimes impossible) to reproduce behavior locally.

Instead we should manage these secrets via ESC so developers can easily unseal the same environment used by CI.

Something like pulumi/esc#92 would be nice but isn't strictly necessary.

This would probably look like:

  • And org-wide "pulumi" environment that all providers can share.
  • Per-provider "pulumi-xyz" environments with provider-level overrides.

Migration could be gradual, with GitHub secrets moving into the org-wide environment as needed.

@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label Dec 10, 2024
@iwahbe iwahbe added kind/enhancement Improvements or new features and removed needs-triage Needs attention from the triage team labels Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

3 participants