distribution/registry
Terin Stock b23dd1ef37 swift: correct segment path generation
When uploading segments to Swift, the registry generates a random file,
by taking the hash of the container path and 32-bytes of random data.
The registry attempts to shard across multiple directory paths, by
taking the first three hex characters as leader.

The implementation in registry, unfortunately, takes the hash of
nothing, and appends it to the path and random data. This results in all
segments being created in one directory.

Fixes: #2407
Fixes: #2311
Signed-off-by: Terin Stock <terinjokes@gmail.com>
2019-06-22 23:44:43 -07:00
..
api Merge pull request #2813 from lucab/ups/spec-json-binary 2019-03-01 14:26:54 -08:00
auth default autoredirect to false 2019-01-04 11:05:12 -08:00
client Merge pull request #2900 from sevki/no-token-err-fix 2019-06-19 19:16:18 -07:00
handlers Merge pull request #2861 from yuwaMSFT2/master 2019-06-19 19:09:29 -07:00
listener [Server] Listen and serve on a unix socket 2015-05-11 16:00:14 +03:00
middleware context: remove definition of Context 2017-08-11 15:53:31 -07:00
proxy Fix gometalint errors 2019-02-04 16:01:04 -08:00
storage swift: correct segment path generation 2019-06-22 23:44:43 -07:00
doc.go Move initialization code from main.go to the registry package 2015-09-09 14:39:31 -07:00
registry.go replace rsc.io/letsencrypt in favour of golang.org/x/crypto 2019-06-04 12:04:18 -07:00
registry_test.go Add support to gracefully shutdown the server 2018-08-20 10:01:26 -07:00
root.go add possibility to clean untagged manifests 2018-01-05 12:20:01 +02:00