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.
38 lines
1.5 KiB
Go
38 lines
1.5 KiB
Go
//go:build !testify_yaml_fail && !testify_yaml_custom
|
|
// +build !testify_yaml_fail,!testify_yaml_custom
|
|
|
|
// Package yaml is just an indirection to handle YAML deserialization.
|
|
//
|
|
// This package is just an indirection that allows the builder to override the
|
|
// indirection with an alternative implementation of this package that uses
|
|
// another implementation of YAML deserialization. This allows to not either not
|
|
// use YAML deserialization at all, or to use another implementation than
|
|
// [gopkg.in/yaml.v3] (for example for license compatibility reasons, see [PR #1120]).
|
|
//
|
|
// Alternative implementations are selected using build tags:
|
|
//
|
|
// - testify_yaml_fail: [Unmarshal] always fails with an error
|
|
// - testify_yaml_custom: [Unmarshal] is a variable. Caller must initialize it
|
|
// before calling any of [github.com/stretchr/testify/assert.YAMLEq] or
|
|
// [github.com/stretchr/testify/assert.YAMLEqf].
|
|
//
|
|
// Usage:
|
|
//
|
|
// go test -tags testify_yaml_fail
|
|
//
|
|
// You can check with "go list" which implementation is linked:
|
|
//
|
|
// go list -f '{{.Imports}}' github.com/stretchr/testify/assert/yaml
|
|
// go list -tags testify_yaml_fail -f '{{.Imports}}' github.com/stretchr/testify/assert/yaml
|
|
// go list -tags testify_yaml_custom -f '{{.Imports}}' github.com/stretchr/testify/assert/yaml
|
|
//
|
|
// [PR #1120]: https://github.com/stretchr/testify/pull/1120
|
|
package yaml
|
|
|
|
import goyaml "gopkg.in/yaml.v3"
|
|
|
|
// Unmarshal is just a wrapper of [gopkg.in/yaml.v3.Unmarshal].
|
|
func Unmarshal(in []byte, out interface{}) error {
|
|
return goyaml.Unmarshal(in, out)
|
|
}
|