New API: Add support spec_version constant

The modules under the tuf/api folder in TUF are an alternative TUF implementation. That's why they should use their own constant for SPECIFICATION_VERSION. This time, I used a list for the SPECIFICATION_VERSION constant in order to retrieve major and minor versions easier. Signed-off-by: Martin Vrachev <[email protected]>
theupdateframework · Jun 9, 2021 · 3bc5ad7 · 3bc5ad7
1 parent 15eb0d9
commit 3bc5ad7
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/tuf/api/__init__.py b/tuf/api/__init__.py
@@ -0,0 +1,12 @@
+"""TUF new API
+
+This package contains all modules related to the TUF refactoring effort.
+
+"""
+# This reference implementation produces metadata intended to conform to
+# version 1.0.0 of the TUF specification, and is expected to consume metadata
+# conforming to version 1.0.0 of the TUF specification.
+# All downloaded metadata must be equal to our supported major version of 1.
+# For example, "1.4.3" and "1.0.0" are supported.  "2.0.0" is not supported.
+# See https://github.com/theupdateframework/specification
+SPECIFICATION_VERSION = ["1", "0", "0"]