We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
firebase-tools: 10.2.2
Platform: Ubuntu
In a project with a firebase extension installed (eg firebase/firestore-bigquery-export), firebase ext:export would ideally product stable env files.
It doesn't, I've not debugged but my hunch this is due to JS dict ordering?
Could the tool be updated to sort the env vars by name before output, so that the files are stable?
firebase ext:export -f git commit -a firebase ext:export -f git diff
Consecutive runs of firebase ext:export would produce extensions/*.env files that are stable.
firebase ext:export
extensions/*.env
The *.env file line order changes with each run.
The text was updated successfully, but these errors were encountered:
This is a very reasonable feature request - I'll take some time to work on it this week.
Sorry, something went wrong.
joehan
Successfully merging a pull request may close this issue.
[REQUIRED] Environment info
firebase-tools: 10.2.2
Platform: Ubuntu
[REQUIRED] Test case
In a project with a firebase extension installed (eg firebase/firestore-bigquery-export), firebase ext:export would ideally
product stable env files.
It doesn't, I've not debugged but my hunch this is due to JS dict ordering?
Could the tool be updated to sort the env vars by name before output, so that the files are stable?
[REQUIRED] Steps to reproduce
[REQUIRED] Expected behavior
Consecutive runs of
firebase ext:export
would produceextensions/*.env
files that are stable.[REQUIRED] Actual behavior
The *.env file line order changes with each run.
The text was updated successfully, but these errors were encountered: