Added attach protocol field in volume attachment schema.

v1/api/swagger/components/schemas/VaAttachProtocol.yaml

@@ -0,0 +1,9 @@
+description: >-
+  Current volume attachment protocol expressed as a string enum value (iscsi, nvmetcp, fuse, fc)
+type: string
+enum:
+  - iscsi
+  - nvmetcp
+  - fuse
+  - fc
+

v1/api/swagger/components/schemas/VolumeAttachment.yaml

@@ -13,6 +13,7 @@ allOf:
       - VolumeTargetIPAddress
       - State
       - FSConfig
+      - AttachProtocol
     properties:
       VolumeID:
         type: string
@@ -63,3 +64,5 @@ allOf:
         type: object
         allOf:
         - $ref: ./VAFSConfig.yaml
+      AttachProtocol:
+        $ref: ./VaAttachProtocol.yaml

v1/pkg/client/README.md

@@ -202,6 +202,7 @@ Class | Method | HTTP request | Description
  - [UserDefinedSteps](docs/UserDefinedSteps.md)
  - [UserOp](docs/UserOp.md)
  - [UserOpEnum](docs/UserOpEnum.md)
+ - [VaAttachProtocol](docs/VaAttachProtocol.md)
  - [VaStateEnum](docs/VaStateEnum.md)
  - [VafsConfig](docs/VafsConfig.md)
  - [Version](docs/Version.md)

v1/pkg/client/api/openapi.yaml

@@ -4764,6 +4764,15 @@ components:
       - TicketExpiryTime
       - UserName
       type: object
+    VaAttachProtocol:
+      description: Current volume attachment protocol expressed as a string enum value
+        (iscsi, nvmetcp, fuse, fc)
+      enum:
+      - iscsi
+      - nvmetcp
+      - fuse
+      - fc
+      type: string
     ProtocolParameters:
       example:
         ISCSI:
@@ -6473,7 +6482,10 @@ components:
           description: File share specific configuration parameters
           nullable: true
           type: object
+        AttachProtocol:
+          $ref: '#/components/schemas/VaAttachProtocol'
       required:
+      - AttachProtocol
       - CHAPSecret
       - CHAPUserName
       - FSConfig

v1/pkg/client/docs/VaAttachProtocol.md

@@ -0,0 +1,10 @@
+# VaAttachProtocol
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
+
+

v1/pkg/client/docs/VolumeAttachment.md

@@ -20,6 +20,7 @@ Name | Type | Description | Notes
 **VolumeTargetIPAddress** | **string** | VolumeTargetIPAddress is the IPV4 address of the iSCSI volume export | 
 **State** | [**VaStateEnum**](VaStateEnum.md) |  | 
 **FSConfig** | Pointer to [**VafsConfig**](VAFSConfig.md) | File share specific configuration parameters | 
+**AttachProtocol** | [**VaAttachProtocol**](VaAttachProtocol.md) |  | 
 
 [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
 

v1/pkg/client/docs/VolumeAttachmentAllOf.md

@@ -15,6 +15,7 @@ Name | Type | Description | Notes
 **VolumeTargetIPAddress** | **string** | VolumeTargetIPAddress is the IPV4 address of the iSCSI volume export | 
 **State** | [**VaStateEnum**](VaStateEnum.md) |  | 
 **FSConfig** | Pointer to [**VafsConfig**](VAFSConfig.md) | File share specific configuration parameters | 
+**AttachProtocol** | [**VaAttachProtocol**](VaAttachProtocol.md) |  | 
 
 [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
 

v1/pkg/client/model_va_attach_protocol.go

@@ -0,0 +1,22 @@
+// (C) Copyright 2021-2023 Hewlett Packard Enterprise Development LP
+
+/*
+ * HPE GreenLake for bare metal API
+ *
+ * This Metal Client REST API provides access to bare metal as-a-service (BMaaS) within a single project context. Clients are able to create fully-provisioned hosts, storage volumes, and project-specific private networks in an isolated project environment.   Project-owned resources that can be accessed via this API include - Host,  Volume, VolumeAttachment, Network (project private), and SSH Key. Each API  call is done within a single project context. The specific Project identifier  must be provided within the header of for each REST call. The server will  validate that the provided authentication credentials (JWTs) are valid  for  the referenced project before any operation is performed. If a single credential is valid for multiple projects, the client must still reference a single project  in the header for each API call.    Clients can also access information about available services and resources through the AvailableResources object. This object provides detailed  information about the OS imaging options, the machine size options, the storage volume options, and data center locations which are needed when creating hosts and volumes.  
+ *
+ * API version: v1
+ * Generated by: OpenAPI Generator (https://openapi-generator.tech)
+ */
+
+package client
+// VaAttachProtocol Current volume attachment protocol expressed as a string enum value (iscsi, nvmetcp, fuse, fc)
+type VaAttachProtocol string
+
+// List of VaAttachProtocol
+const (
+	VAATTACHPROTOCOL_ISCSI VaAttachProtocol = "iscsi"
+	VAATTACHPROTOCOL_NVMETCP VaAttachProtocol = "nvmetcp"
+	VAATTACHPROTOCOL_FUSE VaAttachProtocol = "fuse"
+	VAATTACHPROTOCOL_FC VaAttachProtocol = "fc"
+)

v1/pkg/client/model_volume_attachment.go

@@ -46,4 +46,5 @@ type VolumeAttachment struct {
 	State VaStateEnum `json:"State"`
 	// File share specific configuration parameters
 	FSConfig *VafsConfig `json:"FSConfig"`
+	AttachProtocol VaAttachProtocol `json:"AttachProtocol"`
 }

v1/pkg/client/model_volume_attachment_all_of.go

@@ -33,4 +33,5 @@ type VolumeAttachmentAllOf struct {
 	State VaStateEnum `json:"State"`
 	// File share specific configuration parameters
 	FSConfig *VafsConfig `json:"FSConfig"`
+	AttachProtocol VaAttachProtocol `json:"AttachProtocol"`
 }