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.
26 lines
798 B
Go
26 lines
798 B
Go
//go:build testify_yaml_custom && !testify_yaml_fail && !testify_yaml_default
|
|
// +build testify_yaml_custom,!testify_yaml_fail,!testify_yaml_default
|
|
|
|
// Package yaml is an implementation of YAML functions that calls a pluggable implementation.
|
|
//
|
|
// This implementation is selected with the testify_yaml_custom build tag.
|
|
//
|
|
// go test -tags testify_yaml_custom
|
|
//
|
|
// This implementation can be used at build time to replace the default implementation
|
|
// to avoid linking with [gopkg.in/yaml.v3].
|
|
//
|
|
// In your test package:
|
|
//
|
|
// import assertYaml "github.com/stretchr/testify/assert/yaml"
|
|
//
|
|
// func init() {
|
|
// assertYaml.Unmarshal = func (in []byte, out interface{}) error {
|
|
// // ...
|
|
// return nil
|
|
// }
|
|
// }
|
|
package yaml
|
|
|
|
var Unmarshal func(in []byte, out interface{}) error
|