-
Notifications
You must be signed in to change notification settings - Fork 505
chore: Port to sigs.k8s.io/yaml #3994
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
base: master
Are you sure you want to change the base?
Conversation
Adding the "do-not-merge/release-note-label-needed" label and removing any existing "release-note-none" label because there is a "kind/deprecation" label on the PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
955f119
to
ff8829a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for doing this
as you are replacing this can you move to straight to "sigs.k8s.io/yaml"
and not use the v2?
ff8829a
to
22fea09
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mrueg The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
22fea09
to
7ebc4ea
Compare
|
||
"sigs.k8s.io/release-sdk/object" | ||
yaml "sigs.k8s.io/yaml/goyaml.v2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpanato this uses NewDecoder which is not directly available in ghodds/yaml / sigs.k8s.io/yaml
What type of PR is this?
/kind cleanup
/kind deprecation
What this PR does / why we need it:
Ports from unmaintained gopkg.in/yaml.v2 to sigs.k8s.io/yaml.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?