cloudevents / cloudevents/spec
Extend possible responses for create subscription request with 202
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.9k
- Forks
- 613
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
Currently, the subscription spec documents 2 responses:
- 201 Created successfully
- 400 Invalid request
The subscription create request allows a consumer to subscribe to multiple event types. As there are multiple event types requested, could there be a possibility (to avoid timeout possibilities) to respond with 202 indicating that the subscription create request has been accepted for processing but has not been finished yet?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the subscription specification section that defines the create request and its documented 201 and 400 responses. Determine the normative conditions for accepting asynchronous processing with 202, then update the specification and any associated examples or validation once the expected behavior is agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100