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.

Sign up for GitHub

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

Jump to bottom

Use the same CloudEvent Spec Protocol in the Broker than in the Source #740

Closed
gabo1208 opened this issue May 4, 2022 · 2 comments
Closed

Use the same CloudEvent Spec Protocol in the Broker than in the Source #740

gabo1208 opened this issue May 4, 2022 · 2 comments
Assignees
@gabo1208
Labels
kind/feature-request

Comments

@gabo1208
Copy link
Contributor

gabo1208 commented May 4, 2022

Problem
Right now the RabbitMQ's Broker and Source handle CloudEvents differently, generating inconsistencies and more code to maintain

Persona:
Developers

Exit Criteria
The CloudSpec protocol binding is used in the Broker and in the Source and covers all the required use cases
@gabo1208 gabo1208 mentioned this issue May 4, 2022
Merged
@github-actions
Copy link

github-actions bot commented Aug 3, 2022

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 3, 2022
@gabo1208
Copy link
Contributor Author

gabo1208 commented Aug 4, 2022

this has been done in PR #751

@gabo1208 gabo1208 closed this as completed Aug 4, 2022
@gabo1208 gabo1208 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 4, 2022
@gabo1208 gabo1208 self-assigned this Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gabo1208 gabo1208

Labels
kind/feature-request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gabo1208