You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When querying a volume cia the volume datasource, the snapshot_policy is returned wrong (all fields filled with default 0) and the export_policy is not returned at all.
After doing some investigation, I found out that the data source code is using getVolumeByNameOrCreationToken, which in turn uses a "Describe all volumes" (/v2/projects/{projectNumber}/locations/{locationId}/Volumes) call, which doesn't return all fields.
To get all fields, an individual volume needs to be queried with a "Describe a volume" REST call (/v2/projects/{projectNumber}/locations/{locationId}/Volumes/{volumeId}).
After describing all the volumes and find the relevant ones, we likely have to query each of the volumes in our result set again individually to get all the details.
The text was updated successfully, but these errors were encountered:
When querying a volume cia the volume datasource, the snapshot_policy is returned wrong (all fields filled with default 0) and the export_policy is not returned at all.
After doing some investigation, I found out that the data source code is using
getVolumeByNameOrCreationToken
, which in turn uses a "Describe all volumes" (/v2/projects/{projectNumber}/locations/{locationId}/Volumes
) call, which doesn't return all fields.To get all fields, an individual volume needs to be queried with a "Describe a volume" REST call (
/v2/projects/{projectNumber}/locations/{locationId}/Volumes/{volumeId}
).After describing all the volumes and find the relevant ones, we likely have to query each of the volumes in our result set again individually to get all the details.
The text was updated successfully, but these errors were encountered: