volume spec: fix access_mode field in examples (#24911)

The `volume init` command creates example volume specifications. But one of the values for `capability.access_mode` is not a valid value. Correct the example to match the validation logic.
hashicorp · Jan 22, 2025 · 3e7adba · 3e7adba
1 parent 6873356
commit 3e7adba
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/command/asset/volume.csi.hcl b/command/asset/volume.csi.hcl
@@ -28,7 +28,7 @@ capability {
 }
 
 capability {
-  access_mode     = "single-node-reader"
+  access_mode     = "single-node-reader-only"
   attachment_mode = "block-device"
 }
 

diff --git a/command/asset/volume.csi.json b/command/asset/volume.csi.json
@@ -14,7 +14,7 @@
       "attachment_mode": "file-system"
     },
     {
-      "access_mode": "single-node-reader",
+      "access_mode": "single-node-reader-only",
       "attachment_mode": "block-device"
     }
   ],

diff --git a/command/asset/volume.host.hcl b/command/asset/volume.host.hcl
@@ -19,7 +19,7 @@ capability {
 }
 
 capability {
-  access_mode     = "single-node-reader"
+  access_mode     = "single-node-reader-only"
   attachment_mode = "block-device"
 }
 

diff --git a/command/asset/volume.host.json b/command/asset/volume.host.json
@@ -12,7 +12,7 @@
       "attachment_mode": "file-system"
     },
     {
-      "access_mode": "single-node-reader",
+      "access_mode": "single-node-reader-only",
       "attachment_mode": "block-device"
     }
   ],