Merge pull request #2474 from vikstrous/disable-v1-master
disable schema1 by default, add a config flag to enable it
This commit is contained in:
commit
ef859e1b21
15 changed files with 103 additions and 14 deletions
|
@ -280,6 +280,7 @@ proxy:
|
|||
compatibility:
|
||||
schema1:
|
||||
signingkeyfile: /etc/registry/key.json
|
||||
enabled: true
|
||||
validation:
|
||||
manifests:
|
||||
urls:
|
||||
|
@ -1067,6 +1068,7 @@ username (such as `batman`) and the password for that username.
|
|||
compatibility:
|
||||
schema1:
|
||||
signingkeyfile: /etc/registry/key.json
|
||||
enabled: true
|
||||
```
|
||||
|
||||
Use the `compatibility` structure to configure handling of older and deprecated
|
||||
|
@ -1077,6 +1079,7 @@ features. Each subsection defines such a feature with configurable behavior.
|
|||
| Parameter | Required | Description |
|
||||
|-----------|----------|-------------------------------------------------------|
|
||||
| `signingkeyfile` | no | The signing private key used to add signatures to `schema1` manifests. If no signing key is provided, a new ECDSA key is generated when the registry starts. |
|
||||
| `enabled` | no | If this is not set to true, `schema1` manifests cannot be pushed. |
|
||||
|
||||
## `validation`
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue