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.

Sign up for GitHub

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

Jump to bottom

Secret Support #427

Open

3 tasks

sam-goodwin opened this issue Aug 10, 2023 · 0 comments

Owner

sam-goodwin commented Aug 10, 2023 •

edited

Loading

I don't really want to create a Secret Resource - instead, I want the secret support to feel like local environment variables.

I should be able to create clients that require secrets in module scope without breaking infer or local. E.g. user would use a .env file locally and github secrets when deploying in CI/CD.

const stripeClient = new StripeClient(process.env.STRIPE_API_KEY);

Auto-create Secrets/SecureString Parameters and store credentials in there (perhaps through some config file/.env). Look at SST's Config concept for inspiration.
Load the secrets locally when lambda starts and load into environment variables using top-level await

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment