fix(functions): Refresh credentials before enqueueing first task #907
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.
This change addresses #899 where enqueueing a task from a Cloud Function would fail with an
InvalidArgumentError
error. This was caused by uninitialized credentials being used to in the first task payload sent.The fix explicitly refreshes the credential before accessing the credential, ensuring a valid token or service account email is used in the in the task payload.
This also includes a correction for an f-string typo in the Authorization header construction which could affect Firebase Extensions running with Google Compute Engine credentials.