GoogleDatastoreAdminV1ExportEntitiesRequest

import type { GoogleDatastoreAdminV1ExportEntitiesRequest } from "https://googleapis.deno.dev/v1/datastore:v1.ts";

The request for google.datastore.admin.v1.DatastoreAdmin.ExportEntities.

interface GoogleDatastoreAdminV1ExportEntitiesRequest {

entityFilter?: GoogleDatastoreAdminV1EntityFilter;

labels?: {

[key: string]: string;

};

outputUrlPrefix?: string;

}

§Properties

entityFilter?: GoogleDatastoreAdminV1EntityFilter

[src]

Description of what data from the project is included in the export.

labels?: {

[key: string]: string;

}

[src]

Client-assigned labels.

outputUrlPrefix?: string

[src]

Required. Location for the export metadata and data files. The full resource URL of the external storage location. Currently, only Google Cloud Storage is supported. So output_url_prefix should be of the form: gs://BUCKET_NAME[/NAMESPACE_PATH], where BUCKET_NAME is the name of the Cloud Storage bucket and NAMESPACE_PATH is an optional Cloud Storage namespace path (this is not a Cloud Datastore namespace). For more information about Cloud Storage namespace paths, see Object name considerations. The resulting files will be nested deeper than the specified URL prefix. The final output URL will be provided in the google.datastore.admin.v1.ExportEntitiesResponse.output_url field. That value should be used for subsequent ImportEntities operations. By nesting the data files deeper, the same Cloud Storage bucket can be used in multiple ExportEntities operations without conflict.