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
A user creates a new volume through this TF provider. After the volume is created, the user wants to mount/map the volume to a virtual machine, likely programmatically. To do this, the provider needs to export the NFS mount point or SMB share UNC path. A user can then use this data to create terraform outputs.
To be able to create an output, the provider needs to able to query/provide the mount target. It is preferable if export path and server IP are provided separately.
A quick look at https://cloudvolumesgcp-api.netapp.com/swagger.json suggests that MountPoint_v2.export and MountPoint_v2.server and potentially MountPoint_v2.protocolType are likely the fields of interest.
The text was updated successfully, but these errors were encountered:
User story:
A user creates a new volume through this TF provider. After the volume is created, the user wants to mount/map the volume to a virtual machine, likely programmatically. To do this, the provider needs to export the NFS mount point or SMB share UNC path. A user can then use this data to create terraform outputs.
Example:
NFSv3 : 10.194.0.36:/gifted-cocky-wozniak
SMB : \\cvssmb-0383.cvsdemo.local\nervous-friendly-lovelace
To be able to create an output, the provider needs to able to query/provide the mount target. It is preferable if export path and server IP are provided separately.
A quick look at https://cloudvolumesgcp-api.netapp.com/swagger.json suggests that MountPoint_v2.export and MountPoint_v2.server and potentially MountPoint_v2.protocolType are likely the fields of interest.
The text was updated successfully, but these errors were encountered: