» openstack_sharedfilesystem_share_v2
Use this data source to get the ID of an available Shared File System share.
» Example Usage
data "openstack_sharedfilesystem_share_v2" "share_1" {
name = "share_1"
}
» Argument Reference
-
name- (Optional) The name of the share. -
description- (Optional) The human-readable description for the share. -
project_id- (Optional) The owner of the share. -
snapshot_id- (Optional) The UUID of the share's base snapshot. -
share_network_id- (Optional) The UUID of the share's share network. -
export_location_path- (Optional) The export location path of the share. Available since Manila API version 2.35. -
metadata- (Optional) One or more metadata key and value pairs as a dictionary of strings. -
status- (Optional) A share status filter. A valid value iscreating,error,available,deleting,error_deleting,manage_starting,manage_error,unmanage_starting,unmanage_error,unmanaged,extending,extending_error,shrinking,shrinking_error, orshrinking_possible_data_loss_error. -
is_public- (Optional) The level of visibility for the share. length.
» Attributes Reference
id is set to the ID of the found share. In addition, the following attributes
are exported:
-
name- See Argument Reference above. -
description- See Argument Reference above. -
project_id- See Argument Reference above. -
snapshot_id- See Argument Reference above. -
share_network_id- See Argument Reference above. -
export_location_path- See Argument Reference above. -
metadata- See Argument Reference above. -
status- See Argument Reference above. -
is_public- See Argument Reference above. -
region- The region in which to obtain the V2 Shared File System client. -
availability_zone- The share availability zone. -
share_proto- The share protocol. -
size- The share size, in GBs. -
export_locations- A list of export locations. For example, when a share server has more than one network interface, it can have multiple export locations.