-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Embed CRD files using Go's embed library, remove old auto-gen #9297
Conversation
Bye bye crds.go. Your long lines won't be missed.
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 @fasaxc!
/merge-when-ready squash-commits |
OK, I will merge the pull request when it's ready, squash the commits when I merge it, and leave the branch after I've merged it. |
Removing "merge-when-ready" label due to new commits |
/merge-when-ready |
OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it. |
Removing "merge-when-ready" label due to new commits |
/merge-when-ready squash-commits |
OK, I will merge the pull request when it's ready, squash the commits when I merge it, and leave the branch after I've merged it. |
Description
Go now has a blessed way to embed files in the built executable. Use that in favour of our home-grown script that embedded the CRDs into strings in calicoctl.
Note: the old logic looked bugged, in that not all CRDs were applied by calicoctl. We now include all the CRDs in the libcalico-go/config/crd directory. Hopefully that is what was intended!
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.