The scopes will be included as optional in the connection string as follows: bigquery://project_id/dataset?scopes=scope1,scope2,scope3
No breaking changes have been introduced:
The configFromURI() function has been refactored to meet the same behavior as before.
The scopes in the URI string can be added as optional without affecting the current behavior if the query parameter is not present.
User Case Description
Background: In order to implement an extractor that uses the Gorm BigQuery driver, we require the use of scopes to get data from a view that is being populated by a Google Sheet.
Feature: Being able to authenticate the bigquery client by passing OAuth2 scopes received in the uri.
What did this pull request do?
net/url
library.bigquery://project_id/dataset?scopes=scope1,scope2,scope3
configFromURI()
function has been refactored to meet the same behavior as before.User Case Description
Background: In order to implement an extractor that uses the Gorm BigQuery driver, we require the use of scopes to get data from a view that is being populated by a Google Sheet.
Feature: Being able to authenticate the bigquery client by passing OAuth2 scopes received in the
uri
.Some examples of valid connection strings: