Follow-up to owner field specificaiton

Change-Id: Ib8c1387d88c8b77fbc66fd8924c5b283a40b5d19
This commit is contained in:
Julia Kreger 2018-08-02 11:04:52 -07:00
parent a1a60c80a2
commit 2ba77c9aa9
1 changed files with 5 additions and 4 deletions

View File

@ -57,8 +57,8 @@ likely create their own tooling around list processing.
Data model impact
-----------------
A ``owner`` field would be added to the nodes table as a ``VARCHAR(64)``
and will have a default value of ``None``.
A ``owner`` field would be added to the nodes table as a ``VARCHAR(255)``
and will have a default value of ``null`` in the database.
State Machine Impact
--------------------
@ -74,8 +74,9 @@ updated to allow a user to set and unset the value via the API.
Additionally the GET syntax for the nodes list will be updated to allow a
list of matching nodes to be returned.
POST/PATCH operations to the field will be guarded by a new microversion,
however returning the field will not be guarded by the microversion.
POST/PATCH operations to the field will be guarded by a new microversion.
The field shall not be returned unless the sufficient microversion is supplied
for GET operations.
Client (CLI) impact
-------------------