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

elafros/eventing API to to describe the v1beta2 Flow API #16

Closed
wants to merge 7 commits into from
Closed

elafros/eventing API to to describe the v1beta2 Flow API #16

wants to merge 7 commits into from

Conversation

eobrain
Copy link
Contributor

@eobrain eobrain commented Mar 19, 2018

Fixes Issue # #14

Proposed Changes

  • Remove existing binding API (suggest preserving current code in a new branch before merging this PR)
  • add new v1beta2 eventing flow API

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.

@inlined
Copy link
Contributor

inlined commented Mar 20, 2018

FYI: to help me better learn the code structure I'll take over this task.

@ultrasaurus
Copy link
Contributor

@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.

@eobrain
Copy link
Contributor Author

eobrain commented Mar 21, 2018

Note I just created a new PR
#18
Which just adds the Flow CRD definitions without touching the existing binding API or adding any supporting code.

@eobrain
Copy link
Contributor Author

eobrain commented Mar 21, 2018

I'm closing this PR. We're going to go ahead with #18 instead.

@eobrain eobrain closed this Mar 21, 2018
nachocano pushed a commit to nachocano/eventing that referenced this pull request Feb 25, 2019
creydr pushed a commit to creydr/knative-eventing that referenced this pull request Jan 25, 2023
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants