-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Make documentation for PingSource. #2126
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
Conversation
|
/lgtm |
|
Hey @n3wscott ! Should we also delete the references to CronJobSource in the docs when we merge this in? |
Not yet, wait until post 0.14 release. |
samodell
left a comment
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.
Oof, looks like I wrote these comments and never sent them out. Sorry for the delay on this!
carieshmarie
left a comment
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 your PR! Just a few minor comments/requested changes.
|
|
||
| ## Cleanup | ||
|
|
||
| You can delete the PingSource by entering the following command: |
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.
What exactly are you deleting here? Is it the event source? Or the YAML file? Can we add a noun to the sentence? i.e. "You can delete the Pingsource [NOUN] by entering the following command..."
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.
My guess is the event source is created the same way as a service by applying a yaml file, so deleting the yaml file is deleting the source effectively?
abrennan89
left a comment
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.
Left a few additional comments
| --- | ||
|
|
||
| PingSource example shows how to configure PingSource as event source for | ||
| functions. |
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.
Should this be services or Knative services rather than "functions"?
|
|
||
| ## Create a PingSource | ||
|
|
||
| For each set of ping events you want to request, you need to create an Event |
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.
"For each set of ping events you want to request" - would someone set up a bunch of different PingSource event sources though for each service, or would they have one PingSource and then use the broker and filters to send the events to different services? I don't think it's clear how this is used.
|
|
||
| ## Cleanup | ||
|
|
||
| You can delete the PingSource by entering the following command: |
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.
My guess is the event source is created the same way as a service by applying a yaml file, so deleting the yaml file is deleting the source effectively?
| @@ -0,0 +1,11 @@ | |||
| # This is a very simple Knative Service that writes the input request to its log. | |||
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.
Maybe mention that it's an event input request or something?
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.
it is used all over, maybe we can migrate to a central doc to talk about this?
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.
Maybe time to resurrect #170 ?
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
commit 9a04cb6 Author: Scott Nichols <snichols@vmware.com> Date: Thu Feb 27 07:32:03 2020 -0800 Document ping source.
|
@googlebot I fixed it. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
|
/approve |
|
☝️ I'm triggering /hold |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abrennan89, mattmoor, n3wscott The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
|
@n3wscott is this ready? |
|
@n3wscott I've updated it, here: feel free to squash it in |
|
I would like to merge this and then do a pass on the entire codebase updating to v1alpha2 for pingsource |
|
This is ready, has been for a week |
|
We should (separately) get the eventing WG leads added to OWNERS for this area of the code. I'm surprised Scotty needs approval here. @carieshmarie anything else here? |
|
/unhold |
|
/lgtm |
* Document ping source. * Squashed commit of the following: commit 9a04cb6 Author: Scott Nichols <snichols@vmware.com> Date: Thu Feb 27 07:32:03 2020 -0800 Document ping source. * typo on source. * update image * kail tabs * by name default
Dependent on knative/eventing#2427
Document the renamed instructions for PingSource. Formally called CronJobSource.