Skip to content

Commit

Permalink
Merge pull request #390 from perftool-incubator/dev-kmr2
Browse files Browse the repository at this point in the history
update the registries.json spec
  • Loading branch information
k-rister authored Aug 30, 2024
2 parents b9948f5 + 3081a61 commit a988089
Showing 1 changed file with 12 additions and 2 deletions.
14 changes: 12 additions & 2 deletions spec/registries.json.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,15 +63,25 @@ this:
"tokens": {
"push": "/path/to/public/engines/push/token.json"
},
"tls-verify": true
"tls-verify": true,
"quay": { # optional quay object that is used for quay specific things -- which at this time is all image expiration related (this was in rickshaw-settings.json but it should probably be migrated hear)
"expiration-length": "2w",
"refresh-expiration": {
"token-file": "/path/to/public/engines/refresh/expiration/token.json",
"api-url": "https://quay.io/api/v1/repository/crucible/client-server"
}
}
},
"private": {
"url": "foo.com/crucible/private-engines",
"tokens": { # it is entirely possible (even likely?) that the push and pull token files may be the exact same file, but by specifying them separately the option to use separate tokens is preserved (which may be desirable since the pull token will need to be distributed to the endpoints)
"push": "/path/to/private/engines/push/token.json",
"pull": "/path/to/private/engines/pull/token.json"
},
"tls-verify": true
"tls-verify": true,
"quay": { # this could also have an optional quay object as above
...
}
}
},
"userenvs": [ # this array would contain information to be provided to workshop so it would know how to access base userenv images that have controlled access (by matching against the url?)
Expand Down

0 comments on commit a988089

Please sign in to comment.