-
Notifications
You must be signed in to change notification settings - Fork 225
Conversation
@@ -23,8 +36,7 @@ spec: | |||
apiVersion: serving.knative.dev/v1alpha1 | |||
kind: Service | |||
metadata: | |||
name: message-dumper | |||
namespace: default | |||
name: awssqs-message-dumper |
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.
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.
I was watching that one, my plan was to update once it was merged.
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.
done
2139489
to
1ae86cf
Compare
Is this ready for re-review? It looks like there were some conflicts that slipped in recently, but I can take a look soon if this is ready. |
@evankanderson yes it is ready, I have just resolved the conflicts. Some conflicts were in the documentation so I will test it to be sure it's ok, but otherwise the PR should be ready as is. Thanks in advance! |
/retest |
contrib/awssqs/samples/README.md
Outdated
Deploy the `AwsSqsSource` controller as part of eventing-source's controller. | ||
|
||
```shell | ||
ko -n default apply -f config/ |
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.
This is wrong. It should be ko -n default apply -f contrib/awssqs/
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 should be correct but it's relative to contrib/awssqs. The Deploy section above indicates that commands are run from that dir.
I understand however that you prefer to have the commands relative to the root of the repo (that is the case for instructions in other sources in contrib/). I'll change it.
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.
Done 26f79e2
``` | ||
|
||
You can use [kail](https://github.com/boz/kail/) to tail the logs of the | ||
subscriber. |
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.
Other sources use kubectl log
to monitor the logs of event-display other than asking people to install a new tool kail
. I will suggest to use kubectl log
here for consistency. Of course, you can also add guidances about kail
together with kubectl 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.
Kail is used in all the eventing and eventing-sources documentation, and the previous version of awssqs (this doc is mostly being moved). Examples are gcp pubsub L153 or Camel at L73, L115.
I agree though that the less tools we expect the better, I can do a round and update all these docs, so we remain consistent?
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.
+1 for removing kail, we've been removing it as we go forward, but things linger. Perhaps we can just create an issue to track removing it from all the examples and do it in a followup.
We should get this in asap to stop diverging. Sorry about the time delay. Can you confirm that the moved source is in-sync with the non-contrib version? If so we can merge and then do followup PRs to clean up. |
@n3wscott that'd be great :) This is pretty much the same code as in non-contrib (save for what was necessary to change to make it fully independent inside contrib). I am happy to follow up with improvements / fixes in other PRs. |
@n3wscott I suspect the failure in integration tests is not really due to the PR (the last commits only change markdown files.) I'll try retriggering a bit later, but if you think a retry would work and can /retest for me that'd be awesome. |
/retest |
53f355e
to
979a56e
Compare
@n3wscott looks like this is mergeable now, let me know if you'd like to see the changes about kail done before (see thread). |
Force-push fixing merge conflicts. |
@n3wscott just a kind ping in case this slipped through your radar :) |
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Signed-off-by: Galo Navarro <[email protected]>
Thanks @evankanderson |
/retest |
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.
You might want to do a quick grep for VerbAll
-- I missed one in my previous scan of the code.
@@ -22,24 +22,24 @@ rules: | |||
resources: | |||
- deployments | |||
verbs: | |||
- VerbAll | |||
- * | |||
- apiGroups: | |||
- "" | |||
resources: | |||
- events | |||
verbs: | |||
- VerbAll |
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.
You have another "VerbAll" here
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.
I did miss this one, thanks! I could not find any others.
Signed-off-by: Galo Navarro <[email protected]>
The following is the coverage report on pkg/.
|
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.
/lgtm
Just merged master and this seems to be broken. Can you make one more pass @srvaroa?
Also, the controller never starts as we are not importing the eventing scheme anymore. We need a addtoscheme_eventing_v1alpha1.go inside apis package. You can copy it from gcppubsub. Thanks! |
Thanks for the heads up @nachocano! Pushing these fixes in #406 I can't test them right now on a cluster but will do over the weekend. |
Great! Thanks @srvaroa! |
Along with some documentation cleanup and a couple of simplifications of code. Tested on v0.4.0.