Allow single character repository names
The main goal of this changeset is to allow repository name components to consist of a single character. The number of components allowed and the slash separation requirements have also been clarified. To go along with this simplification, errant constants and unneeded error types have been removed. Signed-off-by: Stephen J Day <stephen.day@docker.com>
This commit is contained in:
parent
bdcae0597f
commit
b54cc5ed47
5 changed files with 57 additions and 46 deletions
|
@ -120,6 +120,12 @@ indicating what is different. Optionally, we may start marking parts of the
|
|||
specification to correspond with the versions enumerated here.
|
||||
|
||||
<dl>
|
||||
<dt>2.0.3</dt>
|
||||
<dd>
|
||||
<li>Allow repository name components to be one character.</li>
|
||||
<li>Clarified that single component names are allowed.</li>
|
||||
</dd>
|
||||
|
||||
<dt>2.0.2</dt>
|
||||
<dd>
|
||||
<li>Added section covering digest format.</li>
|
||||
|
@ -174,12 +180,11 @@ path component is less than 30 characters. The V2 registry API does not
|
|||
enforce this. The rules for a repository name are as follows:
|
||||
|
||||
1. A repository name is broken up into _path components_. A component of a
|
||||
repository name must be at least two lowercase, alpha-numeric characters,
|
||||
repository name must be at least one lowercase, alpha-numeric characters,
|
||||
optionally separated by periods, dashes or underscores. More strictly, it
|
||||
must match the regular expression `[a-z0-9]+(?:[._-][a-z0-9]+)*` and the
|
||||
matched result must be 2 or more characters in length.
|
||||
2. The name of a repository must have at least two path components, separated
|
||||
by a forward slash.
|
||||
must match the regular expression `[a-z0-9]+(?:[._-][a-z0-9]+)*`.
|
||||
2. If a repository name has two or more path components, they must be
|
||||
separated by a forward slash ("/").
|
||||
3. The total length of a repository name, including slashes, must be less the
|
||||
256 characters.
|
||||
|
||||
|
|
|
@ -120,6 +120,12 @@ indicating what is different. Optionally, we may start marking parts of the
|
|||
specification to correspond with the versions enumerated here.
|
||||
|
||||
<dl>
|
||||
<dt>2.0.3</dt>
|
||||
<dd>
|
||||
<li>Allow repository name components to be one character.</li>
|
||||
<li>Clarified that single component names are allowed.</li>
|
||||
</dd>
|
||||
|
||||
<dt>2.0.2</dt>
|
||||
<dd>
|
||||
<li>Added section covering digest format.</li>
|
||||
|
@ -174,12 +180,11 @@ path component is less than 30 characters. The V2 registry API does not
|
|||
enforce this. The rules for a repository name are as follows:
|
||||
|
||||
1. A repository name is broken up into _path components_. A component of a
|
||||
repository name must be at least two lowercase, alpha-numeric characters,
|
||||
repository name must be at least one lowercase, alpha-numeric characters,
|
||||
optionally separated by periods, dashes or underscores. More strictly, it
|
||||
must match the regular expression `[a-z0-9]+(?:[._-][a-z0-9]+)*` and the
|
||||
matched result must be 2 or more characters in length.
|
||||
2. The name of a repository must have at least two path components, separated
|
||||
by a forward slash.
|
||||
must match the regular expression `[a-z0-9]+(?:[._-][a-z0-9]+)*`.
|
||||
2. If a repository name has two or more path components, they must be
|
||||
separated by a forward slash ("/").
|
||||
3. The total length of a repository name, including slashes, must be less the
|
||||
256 characters.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue