ceph-csi/e2e/vendor/sigs.k8s.io/yaml/goyaml.v2
Niels de Vos f87d06ed85 build: move e2e dependencies into e2e/go.mod
Several packages are only used while running the e2e suite. These
packages are less important to update, as the they can not influence the
final executable that is part of the Ceph-CSI container-image.

By moving these dependencies out of the main Ceph-CSI go.mod, it is
easier to identify if a reported CVE affects Ceph-CSI, or only the
testing (like most of the Kubernetes CVEs).

Signed-off-by: Niels de Vos <ndevos@ibm.com>
2025-03-04 17:43:49 +01:00
..
apic.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
decode.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
emitterc.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
encode.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
LICENSE build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
LICENSE.libyaml build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
NOTICE build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
OWNERS build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
parserc.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
readerc.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
README.md build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
resolve.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
scannerc.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
sorter.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
writerc.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
yaml.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
yamlh.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00
yamlprivateh.go build: move e2e dependencies into e2e/go.mod 2025-03-04 17:43:49 +01:00

go-yaml fork

This package is a fork of the go-yaml library and is intended solely for consumption by kubernetes projects. In this fork, we plan to support only critical changes required for kubernetes, such as small bug fixes and regressions. Larger, general-purpose feature requests should be made in the upstream go-yaml library, and we will reject such changes in this fork unless we are pulling them from upstream.

This fork is based on v2.4.0: https://github.com/go-yaml/yaml/releases/tag/v2.4.0

YAML support for the Go language

Introduction

The yaml package enables Go programs to comfortably encode and decode YAML values. It was developed within Canonical as part of the juju project, and is based on a pure Go port of the well-known libyaml C library to parse and generate YAML data quickly and reliably.

Compatibility

The yaml package supports most of YAML 1.1 and 1.2, including support for anchors, tags, map merging, etc. Multi-document unmarshalling is not yet implemented, and base-60 floats from YAML 1.1 are purposefully not supported since they're a poor design and are gone in YAML 1.2.

Installation and usage

The import path for the package is gopkg.in/yaml.v2.

To install it, run:

go get gopkg.in/yaml.v2

API documentation

If opened in a browser, the import path itself leads to the API documentation:

API stability

The package API for yaml v2 will remain stable as described in gopkg.in.

License

The yaml package is licensed under the Apache License 2.0. Please see the LICENSE file for details.

Example

package main

import (
        "fmt"
        "log"

        "gopkg.in/yaml.v2"
)

var data = `
a: Easy!
b:
  c: 2
  d: [3, 4]
`

// Note: struct fields must be public in order for unmarshal to
// correctly populate the data.
type T struct {
        A string
        B struct {
                RenamedC int   `yaml:"c"`
                D        []int `yaml:",flow"`
        }
}

func main() {
        t := T{}
    
        err := yaml.Unmarshal([]byte(data), &t)
        if err != nil {
                log.Fatalf("error: %v", err)
        }
        fmt.Printf("--- t:\n%v\n\n", t)
    
        d, err := yaml.Marshal(&t)
        if err != nil {
                log.Fatalf("error: %v", err)
        }
        fmt.Printf("--- t dump:\n%s\n\n", string(d))
    
        m := make(map[interface{}]interface{})
    
        err = yaml.Unmarshal([]byte(data), &m)
        if err != nil {
                log.Fatalf("error: %v", err)
        }
        fmt.Printf("--- m:\n%v\n\n", m)
    
        d, err = yaml.Marshal(&m)
        if err != nil {
                log.Fatalf("error: %v", err)
        }
        fmt.Printf("--- m dump:\n%s\n\n", string(d))
}

This example will generate the following output:

--- t:
{Easy! {2 [3 4]}}

--- t dump:
a: Easy!
b:
  c: 2
  d: [3, 4]


--- m:
map[a:Easy! b:map[c:2 d:[3 4]]]

--- m dump:
a: Easy!
b:
  c: 2
  d:
  - 3
  - 4