You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to use CFG_JSON_PATH for both file path and secrets contents directly and interchangeably.
CFG_JSON_PATH=/path/to/file
or
CFG_JSON_PATH=the_secrets_themselves
What alternatives have you considered?
None.
Additional context
Coming from Google Cloud environment, it is common for a configuration variables for secrets to contain one of either a) path to a file where secret is stored, b) the secret it self.
One can run app with latest secrets without storing them locally, e.g. with CFG_JSON_PATH=$(gcloud secrets versions access latest --project=boxnow-development --secret=boxnow_customer_app_development_dotenv-api) npm start
Configuru-powered apps would be 100% compatible with secrets injection on GCP
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
No.
What feature would you like to see?
I'd like to use CFG_JSON_PATH for both file path and secrets contents directly and interchangeably.
or
What alternatives have you considered?
None.
Additional context
Coming from Google Cloud environment, it is common for a configuration variables for secrets to contain one of either a) path to a file where secret is stored, b) the secret it self.
Configuru already has A, I'd like to see B too.
Cloud Run secrets can be injected to env var directly.
Google lib google-auth-library and its GOOGLE_APPLICATION_CREDENTIALS supports the same pattern.
Benefits:
CFG_JSON_PATH=$(gcloud secrets versions access latest --project=boxnow-development --secret=boxnow_customer_app_development_dotenv-api) npm start
The text was updated successfully, but these errors were encountered: