feat(functions): Reroute Cloud Tasks to emulator when it is running #2649
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
blidd-google
reviewed
Aug 2, 2024
lahirumaramba
changed the title
This was referenced Sep 15, 2024
Open
Open
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.
Depends on: firebase/firebase-tools#7475
Allows the admin SDK to enqueue and delete tasks within the locally running cloud tasks emulator to provide for easier testing.
API Changes
Introduces
CLOUD_TASKS_EMULATOR_HOSTwhich should contain the host of the Cloud Tasks emulator if it is running. When set, the admin SDK will reroute requests fromenqueueanddeleteto the emulator rather than the production instance.RELEASE NOTES: Added support for the
CLOUD_TASKS_EMULATOR_HOSTenvironment variable.