From 0506bae8fc56dbb5675d48b00fa0ada31fe4b3d9 Mon Sep 17 00:00:00 2001 From: Gabe Rosenhouse Date: Wed, 20 Jul 2016 13:39:51 -0700 Subject: [PATCH] spec: remove CNI_VERSION env var, was never been implemented No one uses this, and it is causing confusion (see #150) --- SPEC.md | 1 - 1 file changed, 1 deletion(-) diff --git a/SPEC.md b/SPEC.md index 74f06e46..06ae36aa 100644 --- a/SPEC.md +++ b/SPEC.md @@ -64,7 +64,6 @@ The operations that the CNI plugin needs to support are: The executable command-line API uses the type of network (see [Network Configuration](#network-configuration) below) as the name of the executable to invoke. It will then look for this executable in a list of predefined directories. Once found, it will invoke the executable using the following environment variables for argument passing: -- `CNI_VERSION`: [Semantic Version 2.0](http://semver.org) of CNI specification. This effectively versions the CNI_XXX environment variables. - `CNI_COMMAND`: indicates the desired operation; either `ADD` or `DEL` - `CNI_CONTAINERID`: Container ID - `CNI_NETNS`: Path to network namespace file