dbmanagement

type CreateStoreRequest struct {

	// project_id is the project within which the store will be created. Project
	// ID is a globally unique ID tied to a project. We do not need User ID
	// because projects exist in only a single organization.
	ProjectId uint64 `protobuf:"varint,1,opt,name=project_id,json=projectId,proto3" json:"project_id,omitempty"`
	// name is a user-facing, memorable name for the store. While most APIs deal
	// strictly in store IDs, the name will be shown in the console and usable
	// within the API.
	Name string `protobuf:"bytes,2,opt,name=name,proto3" json:"name,omitempty"`
	// description is a longer-form, user-facing explanation of what the store is
	// used for - it is used in the console and in generated documentation. We
	// should encourage users to provide a meaningful description.
	Description string `protobuf:"bytes,3,opt,name=description,proto3" json:"description,omitempty"`
	// contains filtered or unexported fields
}

type CreateStoreResponse struct {

	// store_id is a globally unique identifier for a store. Store IDs are
	// assigned by the system when a store is created.
	StoreId uint64 `protobuf:"varint,1,opt,name=store_id,json=storeId,proto3" json:"store_id,omitempty"`
	// contains filtered or unexported fields
}

type DeleteStoreRequest struct {

	// store_id is the globally unique ID of the store to delete.
	StoreId uint64 `protobuf:"varint,1,opt,name=store_id,json=storeId,proto3" json:"store_id,omitempty"`
	// contains filtered or unexported fields
}

type DeleteStoreResponse struct {
	// contains filtered or unexported fields
}

type StoreInfo struct {

	// store_id is a globally unique identifier for a store. Users will of course
	// be able to name their stores with friendly names, but for efficiency's sake
	// the API talks in terms of IDs, which the user can find in the console or
	// via a DescribeStore command. Store IDs are assigned by the system when a
	// store is created.
	StoreId uint64 `protobuf:"varint,1,opt,name=store_id,json=storeId,proto3" json:"store_id,omitempty"`
	// name is a user-facing, memorable name for the store. While most APIs deal
	// strictly in store IDs, the name will be shown in the console and usable
	// within the API.
	Name string `protobuf:"bytes,2,opt,name=name,proto3" json:"name,omitempty"`
	// description is a longer-form, user-facing explanation of what the store is
	// used for - it is used in the console and in generated documentation. We
	// should encourage users to provide a meaningful description.
	Description string `protobuf:"bytes,3,opt,name=description,proto3" json:"description,omitempty"`
	// contains filtered or unexported fields
}