add funcy/functions_go & update docker/distribution

vendor/github.com/docker/distribution/docs/spec/api.md

@@ -1,12 +1,8 @@
-<!--[metadata]>
-+++
-title = "HTTP API V2"
-description = "Specification for the Registry API."
-keywords = ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
-[menu.main]
-parent="smn_registry_ref"
-+++
-<![end-metadata]-->
+---
+title: "HTTP API V2"
+description: "Specification for the Registry API."
+keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
+---
 
 # Docker Registry HTTP API V2
 
@@ -248,7 +244,7 @@ enforce this. The rules for a repository name are as follows:
    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
+3. The total length of a repository name, including slashes, must be less than
    256 characters.
 
 These name requirements _only_ apply to the registry API and should accept a

vendor/github.com/docker/distribution/docs/spec/api.md.tmpl

@@ -1,12 +1,8 @@
-<!--[metadata]>
-+++
-title = "HTTP API V2"
-description = "Specification for the Registry API."
-keywords = ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
-[menu.main]
-parent="smn_registry_ref"
-+++
-<![end-metadata]-->
+---
+title: "HTTP API V2"
+description: "Specification for the Registry API."
+keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced"]
+---
 
 # Docker Registry HTTP API V2
 
@@ -248,7 +244,7 @@ enforce this. The rules for a repository name are as follows:
    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
+3. The total length of a repository name, including slashes, must be less than
    256 characters.
 
 These name requirements _only_ apply to the registry API and should accept a

vendor/github.com/docker/distribution/docs/spec/auth/index.md

@@ -1,13 +1,8 @@
-<!--[metadata]>
-+++
-title = "Docker Registry Token Authentication"
-description = "Docker Registry v2 authentication schema"
-keywords = ["registry, on-prem, images, tags, repository, distribution, authentication, advanced"]
-[menu.main]
-parent="smn_registry_ref"
-weight=100
-+++
-<![end-metadata]-->
+---
+title: "Docker Registry Token Authentication"
+description: "Docker Registry v2 authentication schema"
+keywords: ["registry, on-prem, images, tags, repository, distribution, authentication, advanced"]
+---
 
 # Docker Registry v2 authentication
 

vendor/github.com/docker/distribution/docs/spec/auth/jwt.md

@@ -1,13 +1,8 @@
-<!--[metadata]>
-+++
-title = "Token Authentication Implementation"
-description = "Describe the reference implementation of the Docker Registry v2 authentication schema"
-keywords = ["registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced"]
-[menu.main]
-parent="smn_registry_ref"
-weight=101
-+++
-<![end-metadata]-->
+---
+title: "Token Authentication Implementation"
+description: "Describe the reference implementation of the Docker Registry v2 authentication schema"
+keywords: ["registry, on-prem, images, tags, repository, distribution, JWT authentication, advanced"]
+---
 
 # Docker Registry v2 Bearer token specification
 

vendor/github.com/docker/distribution/docs/spec/auth/oauth.md

@@ -1,13 +1,8 @@
-<!--[metadata]>
-+++
-title = "Oauth2 Token Authentication"
-description = "Specifies the Docker Registry v2 authentication"
-keywords = ["registry, on-prem, images, tags, repository, distribution, oauth2, advanced"]
-[menu.main]
-parent="smn_registry_ref"
-weight=102
-+++
-<![end-metadata]-->
+---
+title: "Oauth2 Token Authentication"
+description: "Specifies the Docker Registry v2 authentication"
+keywords: ["registry, on-prem, images, tags, repository, distribution, oauth2, advanced"]
+---
 
 # Docker Registry v2 authentication using OAuth2
 
@@ -193,4 +188,3 @@ Content-Type: application/json
 
 {"refresh_token":"kas9Da81Dfa8","access_token":"eyJhbGciOiJFUzI1NiIsInR5":"expires_in":900,"scope":"repository:samalba/my-app:pull,repository:samalba/my-app:push"}
 ```
-

vendor/github.com/docker/distribution/docs/spec/auth/scope.md

@@ -1,13 +1,8 @@
-<!--[metadata]>
-+++
-title = "Token Scope Documentation"
-description = "Describes the scope and access fields used for registry authorization tokens"
-keywords = ["registry, on-prem, images, tags, repository, distribution, advanced, access, scope"]
-[menu.main]
-parent="smn_registry_ref"
-weight=103
-+++
-<![end-metadata]-->
+---
+title: "Token Scope Documentation"
+description: "Describes the scope and access fields used for registry authorization tokens"
+keywords: ["registry, on-prem, images, tags, repository, distribution, advanced, access, scope"]
+---
 
 # Docker Registry Token Scope and Access
 
@@ -44,13 +39,23 @@ intended to represent. This type may be specific to a resource provider but must
 be understood by the authorization server in order to validate the subject
 is authorized for a specific resource.
 
+#### Resource Class
+
+The resource type might have a resource class which further classifies the
+the resource name within the resource type. A class is not required and
+is specific to the resource type.
+
 #### Example Resource Types
 
  - `repository` - represents a single repository within a registry. A
 repository may represent many manifest or content blobs, but the resource type
 is considered the collections of those items. Actions which may be performed on
 a `repository` are `pull` for accessing the collection and `push` for adding to
-it.
+it. By default the `repository` type has the class of `image`.
+ - `repository(plugin)` - represents a single repository of plugins within a
+registry. A plugin repository has the same content and actions as a repository.
+ - `registry` - represents the entire registry. Used for administrative actions
+or lookup operations that span an entire registry.
 
 ### Resource Name
 
@@ -83,7 +88,8 @@ scopes.
 ```
 scope                   := resourcescope [ ' ' resourcescope ]*
 resourcescope           := resourcetype  ":" resourcename  ":" action [ ',' action ]*
-resourcetype            := /[a-z]*/
+resourcetype            := resourcetypevalue [ '(' resourcetypevalue ')' ]
+resourcetypevalue       := /[a-z0-9]+/
 resourcename            := [ hostname '/' ] component [ '/' component ]*
 hostname                := hostcomponent ['.' hostcomponent]* [':' port-number]
 hostcomponent           := /([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9])/
@@ -140,4 +146,3 @@ done by fetching an access token using the refresh token. Since the refresh
 token is not scoped to specific resources for an audience, extra care should
 be taken to only use the refresh token to negotiate new access tokens directly
 with the authorization server, and never with a resource provider.
-

vendor/github.com/docker/distribution/docs/spec/auth/token.md

@@ -1,13 +1,8 @@
-<!--[metadata]>
-+++
-title = "Token Authentication Specification"
-description = "Specifies the Docker Registry v2 authentication"
-keywords = ["registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced"]
-[menu.main]
-parent="smn_registry_ref"
-weight=104
-+++
-<![end-metadata]-->
+---
+title: "Token Authentication Specification"
+description: "Specifies the Docker Registry v2 authentication"
+keywords: ["registry, on-prem, images, tags, repository, distribution, Bearer authentication, advanced"]
+---
 
 # Docker Registry v2 authentication via central service
 
@@ -25,7 +20,7 @@ This document outlines the v2 Docker registry authentication scheme:
 5. The client retries the original request with the Bearer token embedded in
    the request's Authorization header.
 6. The Registry authorizes the client by validating the Bearer token and the
-   claim set embedded within it and begins the push/pull session as usual. 
+   claim set embedded within it and begins the push/pull session as usual.
 
 ## Requirements
 
@@ -161,7 +156,7 @@ Defines getting a bearer and refresh token using the token endpoint.
         <code>expires_in</code>
     </dt>
     <dd>
-        (Optional) The duration in seconds since the token was issued that it 
+        (Optional) The duration in seconds since the token was issued that it
         will remain valid.  When omitted, this defaults to 60 seconds.  For
         compatibility with older clients, a token should never be returned with
         less than 60 seconds to live.

vendor/github.com/docker/distribution/docs/spec/implementations.md

@@ -1,8 +1,6 @@
-<!--[metadata]>
-+++
-draft = true
-+++
-<![end-metadata]-->
+---
+published: false
+---
 
 # Distribution API Implementations
 

vendor/github.com/docker/distribution/docs/spec/index.md

@@ -1,13 +1,8 @@
-<!--[metadata]>
-+++
-title = "Reference Overview"
-description = "Explains registry JSON objects"
-keywords = ["registry, service, images, repository,  json"]
-[menu.main]
-parent="smn_registry_ref"
-weight=-1
-+++
-<![end-metadata]-->
+---
+title: "Reference Overview"
+description: "Explains registry JSON objects"
+keywords: ["registry, service, images, repository,  json"]
+---
 
 # Docker Registry Reference
 

vendor/github.com/docker/distribution/docs/spec/json.md

@@ -1,13 +1,9 @@
-<!--[metadata]>
-+++
-draft=true
-title = "Docker Distribution JSON Canonicalization"
-description = "Explains registry JSON objects"
-keywords = ["registry, service, images, repository,  json"]
-[menu.main]
-parent="smn_registry_ref"
-+++
-<![end-metadata]-->
+---
+published: false
+title: "Docker Distribution JSON Canonicalization"
+description: "Explains registry JSON objects"
+keywords: ["registry, service, images, repository,  json"]
+---
 
 
 

vendor/github.com/docker/distribution/docs/spec/manifest-v2-1.md

@@ -1,12 +1,8 @@
-<!--[metadata]>
-+++
-title = "Image Manifest V 2, Schema 1 "
-description = "image manifest for the Registry."
-keywords = ["registry, on-prem, images, tags, repository, distribution, api, advanced, manifest"]
-[menu.main]
-parent="smn_registry_ref"
-+++
-<![end-metadata]-->
+---
+title: "Image Manifest V 2, Schema 1 "
+description: "image manifest for the Registry."
+keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced, manifest"]
+---
 
 # Image Manifest Version 2, Schema 1
 

vendor/github.com/docker/distribution/docs/spec/manifest-v2-2.md

@@ -1,12 +1,8 @@
-<!--[metadata]>
-+++
-title = "Image Manifest V 2, Schema 2 "
-description = "image manifest for the Registry."
-keywords = ["registry, on-prem, images, tags, repository, distribution, api, advanced, manifest"]
-[menu.main]
-parent="smn_registry_ref"
-+++
-<![end-metadata]-->
+---
+title: "Image Manifest V 2, Schema 2 "
+description: "image manifest for the Registry."
+keywords: ["registry, on-prem, images, tags, repository, distribution, api, advanced, manifest"]
+---
 
 # Image Manifest Version 2, Schema 2
 
@@ -34,6 +30,7 @@ the resources they reference:
 - `application/vnd.docker.container.image.v1+json`: Container config JSON
 - `application/vnd.docker.image.rootfs.diff.tar.gzip`: "Layer", as a gzipped tar
 - `application/vnd.docker.image.rootfs.foreign.diff.tar.gzip`: "Layer", as a gzipped tar that should never be pushed
+- `application/vnd.docker.plugin.v1+json`: Plugin config JSON
 
 ## Manifest List
 

vendor/github.com/docker/distribution/docs/spec/menu.md

@@ -1,13 +1,7 @@
-<!--[metadata]>
-+++
-title = "Reference"
-description = "Explains registry JSON objects"
-keywords = ["registry, service, images, repository,  json"]
-type = "menu"
-[menu.main]
-identifier="smn_registry_ref"
-parent="smn_registry"
-weight=7
-+++
-<![end-metadata]-->
-
+---
+title: "Reference"
+description: "Explains registry JSON objects"
+keywords: ["registry, service, images, repository,  json"]
+type: "menu"
+identifier: "smn_registry_ref"
+---