Address PR review feedback on NFS access point OpenAPI spec.

Use real API response samples, correct action enums (SHARE/IN_PROGRESS),
add access-point-specific 400 responses, and add cURL code samples for all
four access point operations.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: sgupta832

specification/resources/nfs/examples/curl/nfs_access_point_create.yml

@@ -0,0 +1,7 @@
+lang: cURL
+source: |-
+  curl -X POST \
+    -H "Content-Type: application/json" \
+    -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
+    -d '{"name": "other-vpc", "path": "/other-vpc", "vpc_id": "3f34cdb2-1e4f-4100-b5c7-f55f2762085f", "access_policy": {"anonuid": 65534, "anongid": 65534, "protocols": ["NFS4", "NFS"], "squash_config": "ROOT_SQUASH", "identity_enforcement_enabled": false}}' \
+    "https://api.digitalocean.com/v2/nfs/shares/baf4827c-6fa9-456f-9dbd-9ddfcacd0720/access_points"

specification/resources/nfs/examples/curl/nfs_access_point_delete.yml

@@ -0,0 +1,6 @@
+lang: cURL
+source: |-
+  curl -X DELETE \
+    -H "Content-Type: application/json" \
+    -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
+    "https://api.digitalocean.com/v2/nfs/access_points/7659ce91-354d-4f61-9cda-ae2c7feb61d9"

specification/resources/nfs/examples/curl/nfs_access_point_get.yml

@@ -0,0 +1,6 @@
+lang: cURL
+source: |-
+  curl -X GET \
+    -H "Content-Type: application/json" \
+    -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
+    "https://api.digitalocean.com/v2/nfs/access_points/becd9f04-8afa-4ccd-b03e-9676447df603"

specification/resources/nfs/examples/curl/nfs_access_point_list.yml

@@ -0,0 +1,6 @@
+lang: cURL
+source: |-
+  curl -X GET \
+    -H "Content-Type: application/json" \
+    -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
+    "https://api.digitalocean.com/v2/nfs/shares/baf4827c-6fa9-456f-9dbd-9ddfcacd0720/access_points"

specification/resources/nfs/models/access_point_request.yml

@@ -9,15 +9,15 @@ properties:
       characters and match `^[a-zA-Z0-9][a-zA-Z0-9-]{1,61}[a-zA-Z0-9]$`.
       The name `default` is reserved (case-insensitive) for the implicit default
       access point created with each share.
-    example: "team-a"
+    example: "other-vpc"
   path:
     type: string
     description: |
       The export sub-path. Must start with `/`, must not be exactly `/` (reserved
       for the default access point), must be at most 1024 characters, may contain
       only alphanumerics, `-`, `_`, `.`, and `/`, and must not contain `..` path
       segments.
-    example: "/team-a"
+    example: "/other-vpc"
   access_policy:
     $ref: "access_policy.yml"
   vpc_id:
@@ -26,7 +26,7 @@ properties:
       Required. The VPC this access point will be pinned to. A storage gateway is
       provisioned (or reused) in this VPC, and the access point becomes mountable from
       this VPC regardless of whether the parent share is currently attached to it.
-    example: "796c6fe3-2a1d-4da2-9f3e-38239827dc91"
+    example: "3f34cdb2-1e4f-4100-b5c7-f55f2762085f"
 required:
   - name
   - path

specification/resources/nfs/models/access_point_response.yml

@@ -11,7 +11,7 @@ properties:
   name:
     type: string
     description: The human-readable name of the access point. Must be unique per share.
-    example: "team-a"
+    example: "other-vpc"
   share_id:
     type: string
     format: uuid
@@ -21,7 +21,7 @@ properties:
   path:
     type: string
     description: The export sub-path for this access point (always starts with `/`).
-    example: "/team-a"
+    example: "/other-vpc"
   status:
     type: string
     enum: ["ACCESS_POINT_CREATING", "ACCESS_POINT_ACTIVE", "ACCESS_POINT_FAILED", "ACCESS_POINT_DELETED"]
@@ -41,10 +41,11 @@ properties:
     example: "2023-01-01T00:00:00Z"
   updated_at:
     type: string
-    format: date-time
-    description: The timestamp when the access point was last updated.
+    description: |
+      The timestamp when the access point was last updated. May be empty while the
+      access point is still being created.
     readOnly: true
-    example: "2023-01-01T01:00:00Z"
+    example: "2026-06-25T08:11:16Z"
   is_default:
     type: boolean
     description: Whether this is the share's default access point.
@@ -53,11 +54,10 @@ properties:
   vpc_id:
     type: string
     description: |
-      The VPC this access point is pinned to. Every non-default access point owns its
-      own storage gateway in this VPC and is independent of the parent share's VPC
-      lifecycle: it remains mountable from this VPC regardless of whether the share is
-      currently attached to it.
-    example: "796c6fe3-2a1d-4da2-9f3e-38239827dc91"
+      The VPC this access point is pinned to. Omitted on the default access point.
+      Every non-default access point owns its own storage gateway in this VPC and
+      is independent of the parent share's VPC lifecycle.
+    example: "3f34cdb2-1e4f-4100-b5c7-f55f2762085f"
 required:
   - id
   - name

specification/resources/nfs/models/nfs_action.yml

@@ -5,36 +5,39 @@ properties:
   id:
     type: string
     description: The unique identifier of the action.
-    example: "1"
+    example: "084c3b9c-2382-441b-92d4-10b095bb5d7c"
   region_slug:
     type: string
     description: The DigitalOcean region slug where the resource is located.
-    example: "atl1"
+    example: "s2r1"
   resource_id:
     type: string
     format: uuid
     description: The unique identifier of the resource on which the action is being performed.
-    example: "a1b2c3d4-e5f6-4a5b-9c8d-1e2f3a4b5c6d"
+    example: "7659ce91-354d-4f61-9cda-ae2c7feb61d9"
   resource_type:
     type: string
-    enum: ["network_file_share", "network_file_share_snapshot"]
-    description: The type of resource on which the action is being performed.
-    example: "network_file_share"
+    enum: ["SHARE", "SNAPSHOT"]
+    description: |
+      The type of resource on which the action is being performed. Access point
+      mutations return `SHARE` with `resource_id` set to the access point UUID.
+    example: "SHARE"
   started_at:
     type: string
     format: date-time
     description: The timestamp when the action was started.
-    example: "2025-10-14T11:55:31.615157397Z"
+    example: "2026-06-25T08:11:12Z"
   status:
     type: string
-    enum: ["in-progress", "completed", "errored"]
+    enum: ["IN_PROGRESS", "COMPLETED", "ACTION_FAILED"]
     description: The current status of the action.
-    example: "in-progress"
+    example: "IN_PROGRESS"
   type:
     type: string
     description: |
-      The type of action being performed. Share actions use values such as resize
-      and snapshot. Access point mutations use CREATE_ACCESS_POINT and DELETE_ACCESS_POINT.
+      The type of action being performed. Share actions use values such as
+      `RESIZE_SHARE` and `CREATE_SHARE`. Access point mutations use
+      `CREATE_ACCESS_POINT` and `DELETE_ACCESS_POINT`.
     example: "CREATE_ACCESS_POINT"
 required:
   - region_slug

specification/resources/nfs/models/nfs_api_error.yml

@@ -0,0 +1,15 @@
+---
+type: object
+description: A standard NFS API error response object.
+properties:
+  code:
+    type: string
+    description: A service-defined error code.
+    example: "MISSING_NAME"
+  message:
+    type: string
+    description: A human-readable description of the error.
+    example: "name is required"
+required:
+  - code
+  - message

specification/resources/nfs/nfs_access_point_create.yml

@@ -23,7 +23,7 @@ parameters:
       type: string
       format: uuid
     description: The unique identifier of the NFS share.
-    example: "0a1b2c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d"
+    example: "baf4827c-6fa9-456f-9dbd-9ddfcacd0720"
 
 requestBody:
   required: true
@@ -34,22 +34,22 @@ requestBody:
       examples:
         Basic Access Point:
           value:
-            name: "team-a"
-            path: "/team-a"
-            vpc_id: "796c6fe3-2a1d-4da2-9f3e-38239827dc91"
+            name: "other-vpc"
+            path: "/other-vpc"
+            vpc_id: "3f34cdb2-1e4f-4100-b5c7-f55f2762085f"
             access_policy:
               anonuid: 65534
               anongid: 65534
-              protocols: ["NFS4"]
+              protocols: ["NFS4", "NFS"]
               squash_config: "ROOT_SQUASH"
-              identity_enforcement_enabled: true
+              identity_enforcement_enabled: false
 
 responses:
   '201':
     $ref: 'responses/access_point_create.yml'
 
   '400':
-    $ref: 'responses/bad_request.yml'
+    $ref: 'responses/access_point_bad_request.yml'
 
   '401':
     $ref: '../../shared/responses/unauthorized.yml'
@@ -69,6 +69,9 @@ responses:
   default:
     $ref: '../../shared/responses/unexpected_error.yml'
 
+x-codeSamples:
+  - $ref: 'examples/curl/nfs_access_point_create.yml'
+
 security:
   - bearer_auth:
       - "nfs:create"

specification/resources/nfs/nfs_access_point_delete.yml

@@ -23,14 +23,14 @@ parameters:
       type: string
       format: uuid
     description: The unique identifier of the NFS access point.
-    example: "a1b2c3d4-e5f6-4a5b-9c8d-1e2f3a4b5c6d"
+    example: "7659ce91-354d-4f61-9cda-ae2c7feb61d9"
 
 responses:
   "200":
     $ref: "responses/access_point_delete.yml"
 
   "400":
-    $ref: "responses/bad_request.yml"
+    $ref: "responses/access_point_bad_request.yml"
 
   "401":
     $ref: "../../shared/responses/unauthorized.yml"
@@ -47,6 +47,9 @@ responses:
   default:
     $ref: "../../shared/responses/unexpected_error.yml"
 
+x-codeSamples:
+  - $ref: "examples/curl/nfs_access_point_delete.yml"
+
 security:
   - bearer_auth:
       - "nfs:delete"