[Task]: Support OrganizationId support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Other (Anything else which does not match above categories)
Please select the aspect the issue is related to
Aspect/Other (Anything else which does not match above categories)
Description
Add OrganizationId support. We should add fields related to orgId to WebSub APIs and WebBroker APIs. This should also be addressed in the Kafka topics we create as well (Currently, ApiName + ApiTopic will correspond to a Kafka topic. This should be modified as ApiName + orgId + ApiTopic).
Contributor guide
No contributing guide indexed for this repository
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
Trace the WebSub APIs, WebBroker APIs, and Kafka topic creation paths mentioned in the issue, starting with how ApiName and ApiTopic are currently combined. Add OrganizationId handling across those paths and verify that the resulting Kafka topic uses ApiName, orgId, and ApiTopic consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100