mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
30 lines
594 B
Go
30 lines
594 B
Go
package restful
|
|
|
|
import (
|
|
"fmt"
|
|
"regexp"
|
|
)
|
|
|
|
var (
|
|
customVerbReg = regexp.MustCompile(":([A-Za-z]+)$")
|
|
)
|
|
|
|
func hasCustomVerb(routeToken string) bool {
|
|
return customVerbReg.MatchString(routeToken)
|
|
}
|
|
|
|
func isMatchCustomVerb(routeToken string, pathToken string) bool {
|
|
rs := customVerbReg.FindStringSubmatch(routeToken)
|
|
if len(rs) < 2 {
|
|
return false
|
|
}
|
|
|
|
customVerb := rs[1]
|
|
specificVerbReg := regexp.MustCompile(fmt.Sprintf(":%s$", customVerb))
|
|
return specificVerbReg.MatchString(pathToken)
|
|
}
|
|
|
|
func removeCustomVerb(str string) string {
|
|
return customVerbReg.ReplaceAllString(str, "")
|
|
}
|