Method: projects.locations.backupVaults.dataSources.fetchAccessToken
Stay organized with collections
Save and categorize content based on your preferences.
- HTTP request
- Path parameters
- Request body
- Response body
- Authorization scopes
- IAM Permissions
- Try it!
Internal only. Fetch access token for a given data source.
HTTP request
POST https://backupdr.googleapis.com/v1/{name=projects/*/locations/*/backupVaults/*/dataSources/*}:fetchAccessToken
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
name |
Required. The resource name for the location for which static IPs should be returned. Must be in the format 'projects/*/locations/*/backupVaults/*/dataSources'. |
Request body
The request body contains data with the following structure:
| JSON representation |
|---|
{ "generationId": integer } |
| Fields | |
|---|---|
generationId |
Required. The generation of the backup to update. |
Response body
Response message for dataSources.fetchAccessToken.
If successful, the response body contains data with the following structure:
| JSON representation |
|---|
{ "readLocation": string, "writeLocation": string, "token": string, "expireTime": string } |
| Fields | |
|---|---|
readLocation |
The location in bucket that can be used for reading. |
writeLocation |
The location in bucket that can be used for writing. |
token |
The downscoped token that was created. |
expireTime |
The token is valid until this time. Uses RFC 3339, where generated output will always be Z-normalized and use 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted. Examples: |
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
IAM Permissions
Requires the following IAM permission on the name resource:
backupdr.bvdataSources.fetchAccessToken
For more information, see the IAM documentation.