Skip to content

Adding Knative Eventing Object Model targeting 0.1 release.#482

Merged
knative-prow-robot merged 68 commits into
knative:masterfrom
n3wscott:push_raw_spec
Oct 23, 2018
Merged

Adding Knative Eventing Object Model targeting 0.1 release.#482
knative-prow-robot merged 68 commits into
knative:masterfrom
n3wscott:push_raw_spec

Conversation

@n3wscott
Copy link
Copy Markdown
Contributor

@n3wscott n3wscott commented Oct 1, 2018

Adding https://docs.google.com/document/d/1JZtFkz_C3orG9IfDxxGkAmuuGxUQ434ji-rdl3oKObE/edit to the repo as a markdown file.

Release Note

NONE

@knative-prow-robot knative-prow-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Oct 1, 2018
@n3wscott n3wscott changed the title object model spec doc to markdown. [WIP] object model spec doc to markdown. Oct 1, 2018
@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 1, 2018
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 1, 2018
@knative-prow-robot knative-prow-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 1, 2018
@n3wscott n3wscott changed the title [WIP] object model spec doc to markdown. Adding object model spec doc to markdown. Oct 1, 2018
@knative-prow-robot knative-prow-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 1, 2018
@googlebot
Copy link
Copy Markdown

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@grantr
Copy link
Copy Markdown
Contributor

grantr commented Oct 22, 2018

Authors and co-authors @evankanderson @n3wscott @scothis @matzew have all accepted the CLA on other PRs. Manually setting CLA to yes.

@grantr grantr added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Oct 22, 2018
Copy link
Copy Markdown
Member

@evankanderson evankanderson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

Missed these yesterday, but this looks close enough to go in.

Comment thread docs/spec/spec.md

##### Conditions

- **Ready.**
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At least 9 forward, and the 10th which is not Ready may or may not forward.

Comment thread docs/spec/spec.md
- **CallActive.** True if the call is sinking events without error.
- **Resolved.**

#### Events
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's why I wonder if removing these Events would make it easier to read the spec without losing any utility.

Comment thread docs/spec/spec.md

| Field | Type | Description | Limitations |
| ----- | --------------- | ----------- | ----------- |
| ref\* | ObjectReference | | |
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ProvisionerReference is only used in Channel's spec. Compare:

apiVersion: eventing.knative.dev/v1alpha1
kind: Channel
metadata:
  name: cc-payments
spec:
  provisioner:
    apiVersion: eventing.knative.dev/v1alpha1
    kind: ClusterChannelProvisioner
    name: kafka

vs

apiVersion: eventing.knative.dev/v1alpha1
kind: Channel
metadata:
  name: cc-payments
spec:
  provisioner:
    clusterName: kafka  # Allows for name later

I have a slight preference for the smaller and simpler format, since we don't really want to distinguish between more than two possible types (ChannelProvisioner and ClusterChannelProvisioner).

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2018
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: evankanderson, n3wscott

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2018
@grantr grantr added cla: yes Indicates the PR's author has signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Oct 23, 2018
@googlebot googlebot added cla: no Indicates the PR's author has not signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Oct 23, 2018
@googlebot
Copy link
Copy Markdown

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot googlebot added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Oct 23, 2018
@knative-prow-robot knative-prow-robot merged commit b6219ae into knative:master Oct 23, 2018
adamharwayne pushed a commit to Harwayne/knative-eventing that referenced this pull request Oct 23, 2018
adamharwayne pushed a commit to Harwayne/knative-eventing that referenced this pull request Oct 23, 2018
adamharwayne pushed a commit to Harwayne/knative-pkg that referenced this pull request Oct 23, 2018
adamharwayne pushed a commit to Harwayne/knative-eventing that referenced this pull request Oct 24, 2018
knative-prow-robot pushed a commit that referenced this pull request Oct 25, 2018
* Change Channelable to match the definition in #482.

* No longer use the subscribable interface.

* Move the Channelable duck type into the eventing repo.
matzew added a commit to matzew/eventing that referenced this pull request Mar 11, 2020
Co-authored-by: Paul Morie <pmorie@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.