Fix auth.parameters()
in sync streams
#369
Open
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.
With sync streams, we expose parameters as a pair of functions:
.parameters()
to return the raw JSON object as a string and.parameter(path)
to extract values from that JSON object.For JWT tokens, lookups with
.parameter
were broken because they only searched in aparameters
sub-object of the JWT instead of the top-level structure. So if one doesWHERE project_id = auth.parameter('project_id')
for instance, the JWT would have to encode a{..., "parameters": {"project_id": "value"}}
pair instead of being able to useproject_id
at the top-level.This is inconsistent and not the behavior we want, this fixes that.