-
Notifications
You must be signed in to change notification settings - Fork 452
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
Infra Week: Create Utility Script for Exporting ENV Variables and Update Pulumi Scripts #2628
Comments
We probably want to use the methods described here? https://developer.1password.com/docs/cli/secrets-environment-variables |
The repos affected
Exceptions to be handled
|
Note: I'll update the pulumi scripts as part of #2627, so this ticket can just handle the script for local development |
There are POCs for loading the env variables while running pulumi up locally in the linked PRs. Moving to blocked until 2627 is finished up since there is a decent amount of overlap |
This is no longer needed |
User Story:
As a developer, I want to create a utility script that pulls and exports all relevant ENV variables for any environment to local ENVs and update Pulumi scripts to read these variables, so that I can run
pulumi up
from my local environment for review, staging, and production using the correct variables.!! Note from Lucian !! : I'll update the pulumi scripts as part of #2627, so this ticket can just handle the script for local development. Or really, setting up a .env.local with the right 1password paths and then altering the package.json commands to use the 1password utility, and making sure 1password has good default entries for local dev. See https://developer.1password.com/docs/cli/secrets-environment-variables/
Acceptance Criteria:
GIVEN the utility script and updated Pulumi scripts,
WHEN I run the script,
THEN all relevant environment variables should be pulled and exported to my local environment, and the Pulumi scripts should use these variables.
Tech Details:
NEXT_PUBLIC_MAX_LEGACY_ROUND_ID
.Open Questions:
Should the script handle any environment-specific logic?
Are there additional environment variables that need to be considered?
Notes/Assumptions:
The text was updated successfully, but these errors were encountered: