Enable passing CloudEvents headers ('CE-*')#180
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@evankanderson I started an effort to centralize the http bit for the buses over at #175. I added support for the common I can port your change on top of that PR if you'd like to close this one. |
|
That sounds fine with me; what's the ETA on that PR? I did this as part of trying to thread cloud events though the whole system. What's the rationale behind removing most headers in the bus? It seems like 2 of 3 implementations do this, but it seems hostile to extension (as we're seeing with cloud events). |
|
/hold |
|
Closing in favor of #175 |
Update catalogsource yaml to v0.7.1
Also cleans up some
go vetwarnings.THIS IS NOT TESTED. Mostly because we don't seem to have any test cases yet for these buses. It seems like it would be useful to have a small test harness that accepts a set of HTTP requests and sends them to the bus then verifies that the correct messages were received by standing up a listening HTTP server and looping back from the bus to the handler.
Works towards #53
Proposed Changes
CE-headers to the whitelist on the two buses that use a whitelist for handling messages. Long term, I'd like to see the buses move towards a blacklist model in terms of header passing, both in light of Make extension attributes siblings to our attributes cloudevents/spec#225 and to enable other development and experimentation without needing to rebuild the controller.<--
/assign @scothis
/assign @ericbottard
-->