katenary/internal/generator/labels/labelstructs/configMap.go

package labelstructs

import "gopkg.in/yaml.v3"

type ConfigMapFiles []string

func ConfigMapFileFrom(data string) (ConfigMapFiles, error) {
	var mapping ConfigMapFiles
	if err := yaml.Unmarshal([]byte(data), &mapping); err != nil {
		return nil, err
	}
	return mapping, nil
}
chore(convention): Respect Go convention, package name should be lowercase 2025-07-06 14:34:16 +02:00			`package labelstructs`
Add more tests, refactor to fix problems Signed-off-by: Patrice Ferlet <metal3d@gmail.com> 2024-04-24 20:55:27 +02:00
Use real types to parse labels We were using `yaml.Unmarshal` on basic types or inline structs. This was not efficient and not clear to defined what we expect in labels. We now use types to unmarshal the labels. Only the `values` label is, at this time, parsed by GetValuesFromLabel because this `utils` function is clearly a special case. 2024-04-24 23:06:45 +02:00			`import "gopkg.in/yaml.v3"`

fix(katenaryfile): Fix parsing katenary file It seems that "json" annotation fails to get dashed names (like configmap-files). That means that all labels in katernay.yaml file couldn't be parsed. Using `yaml` annotaiton fixes the problem. Fixes #144. 2025-07-15 21:13:22 +02:00			`type ConfigMapFiles []string`
Use real types to parse labels We were using `yaml.Unmarshal` on basic types or inline structs. This was not efficient and not clear to defined what we expect in labels. We now use types to unmarshal the labels. Only the `values` label is, at this time, parsed by GetValuesFromLabel because this `utils` function is clearly a special case. 2024-04-24 23:06:45 +02:00
fix(katenaryfile): Fix parsing katenary file It seems that "json" annotation fails to get dashed names (like configmap-files). That means that all labels in katernay.yaml file couldn't be parsed. Using `yaml` annotaiton fixes the problem. Fixes #144. 2025-07-15 21:13:22 +02:00			`func ConfigMapFileFrom(data string) (ConfigMapFiles, error) {`
			`var mapping ConfigMapFiles`
Use real types to parse labels We were using `yaml.Unmarshal` on basic types or inline structs. This was not efficient and not clear to defined what we expect in labels. We now use types to unmarshal the labels. Only the `values` label is, at this time, parsed by GetValuesFromLabel because this `utils` function is clearly a special case. 2024-04-24 23:06:45 +02:00			`if err := yaml.Unmarshal([]byte(data), &mapping); err != nil {`
			`return nil, err`
			`}`
			`return mapping, nil`
Add more tests, refactor to fix problems Signed-off-by: Patrice Ferlet <metal3d@gmail.com> 2024-04-24 20:55:27 +02:00			`}`