vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Initial implementation of storage layer path mapper

Browse source 
We've added a path mapper to support simple mapping between path objects used
in the storage layer and the underlying file system. The target of this is to
ensure that paths are only calculated in a single place and their format is
separated from the data that makes up the path components.

This commit only includes spec implementation to support layer reads. Further
specs will come along with their implementations.
This commit is contained in:
Stephen J Day 2014-11-13 15:16:54 -08:00
parent 0c999bd2da
commit 8e44c1d209
4 changed files with 231 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
common/names.go
View file

@ -9,6 +9,10 @@ import (
// separated by one period, dash or underscore.
var RepositoryNameComponentRegexp = regexp.MustCompile(`[a-z0-9]{2,}(?:[._-][a-z0-9]+)*`)
// TODO(stevvooe): RepositoryName needs to be limited to some fixed length.
// Looking path prefixes and s3 limitation of 1024, this should likely be
// around 512 bytes. 256 bytes might be more manageable.
// RepositoryNameRegexp builds on RepositoryNameComponentRegexp to allow 2 to
// 5 path components, separated by a forward slash.
var RepositoryNameRegexp = regexp.MustCompile(`(?:` + RepositoryNameComponentRegexp.String() + `/){1,4}` + RepositoryNameComponentRegexp.String())