SPEC: use correct GC field name.

The SPEC and libcni disagreed on the name to use for still-valid attachments. Change the spec to be aligned with libcni. Signed-off-by: Casey Callendrello <[email protected]>
containernetworking · Jul 1, 2024 · 6a68851 · 6a68851
1 parent d5c71ad
commit 6a68851
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/SPEC.md b/SPEC.md
@@ -387,7 +387,7 @@ The runtime MUST NOT use GC as a substitute for DEL. Plugins may be unable to cl
 
 The runtime must provide a JSON-serialized plugin configuration object (defined below) on standard in. It contains an additional key;
 
-- `cni.dev/attachments` (array of objects): The list of **still valid** attachments to this network:
+- `cni.dev/valid-attachments` (array of objects): The list of **still valid** attachments to this network:
     - `containerID` (string): the value of CNI_CONTAINERID as provided during the CNI ADD operation
     - `ifname` (string): the value of CNI_IFNAME as provided during the CNI ADD operation
 
@@ -496,7 +496,7 @@ For attachment-specific operations (ADD, DEL, CHECK), additional field requireme
 - `capabilities`: must not be set
 
 For GC operations:
-- `cni.dev/attachments`: as specified in section 2.
+- `cni.dev/valid-attachments`: as specified in section 2.
 
 All other fields not prefixed with `cni.dev/` should be passed through unaltered.