Fix: moving Bandada's vkey inside cloud function #332
Merged
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.
name: moving Bandada's vkey inside cloud function
about: Open a PR for p0tion
Description
We are having some issues when trying to deploy the cloud functions in our production environment. According to a Firebase team comment in a Github issue, it might be related to having large data and actions in the global scope instead of inside the function (check comment here).
Fixes # (issue)
How Has This Been Tested?
I have not been able to test it due to the fact that the function deployment in prod environment happens when we merge the respective PRs.
Checklist: