-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Support for env and secret files #137
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Aug 31, 2023
Closed
Closed
Great stuff and great work! We really like this project at our company and just started to use it. Do you have any idea when this will be released? |
@Gurey thanks for the kind feedback. Hopefully in next week or so, I'm just finishing up some migration tooling. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for function environment vars. Solution:
environment
folder.env
,.env.local
and.secret.local
files in this dirproject.json
to copy them from parent firebase appenvironment
folder when functions are builtsync
generator to auto-rename the glob assets input dir rule if parent firebase app is renamedgetconfig
target to place.runtimeconfig.json
in the firebase appenvironment
dirfirebase.json
to haveignore: [ "*.local" ]
rule to prevent local files being deployedOutcome is that functions get the common environment vars copied from the parent firebase app to their
dist
folder, which allows:.env*
files to be deployed with function code*.local
and.runtimeconfig.json
files to be accessible to firebase emulator when serving locallyDocumentation updates also in this PR.