Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: How to parse multiple yaml resource in a single file #71

Closed
amustaque97 opened this issue Jan 31, 2022 · 4 comments
Closed

Question: How to parse multiple yaml resource in a single file #71

amustaque97 opened this issue Jan 31, 2022 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@amustaque97
Copy link

Hi team,

I have a single yaml file let us suppose config.yml and it has multiple yaml configuration separated by --- (three dashes). I'm using YAMLToJSON function to convert it to json but it is not returning 2nd resource config.

yaml/yaml.go

Line 111 in 9535b3b

func YAMLToJSON(y []byte) ([]byte, error) {

Does anyone how to do it?
Thanks

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 1, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 31, 2022
@amustaque97
Copy link
Author

There is no response from maintainer. Closing this issue.

@amustaque97 amustaque97 closed this as not planned Won't fix, can't repro, duplicate, stale May 31, 2022
@SVilgelm
Copy link

@amustaque97 the PR I just raised yesterday should help in this: #79

Decoder supports reading from stream, so something like this:

d := yaml.NewDecoder(reader)
var objs []any
for {
    var obj any
    err := d.Decode(&obj)
    if errors.Is(err, io.EOF) {
        break
    } else if err != nil {
        panic(err)
    }
    objs = append(objs, obj)
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants