-
Notifications
You must be signed in to change notification settings - Fork 593
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
elafros/eventing API to to describe the v1beta2 Flow API #16
Conversation
FYI: to help me better learn the code structure I'll take over this task. |
@eobrain my understanding was that the binding work was going to be moved to a sub-directory. Please remove that change from this PR and just add the Flow CRD definition. I'll work with @vaikas-google on a directory structure that makes sense for where we are. |
Note I just created a new PR |
I'm closing this PR. We're going to go ahead with #18 instead. |
Merge upstream/master.
The workflows should be removed in the same way as in create-release-branch.sh so that they're not executed when pushing to release-next and release-next-ci branches.
Fixes Issue # #14
Proposed Changes
Note, this code compiles and
bazel run :everything.apply
executes. But a few key parts of the runtime code have been commented out, so nothing actually gets deployed to the Kubernetes cluster.