influxdata / influxdata/openapi
chore: investigate if cloud limit schema can be merged with quartz' orgLimit
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Apparently they roughly equate to similar apis. Seems we should prefer quartz' definitions if it is decided they can be merged as it is more granular and descriptive (useful to clients). Currently holding off on merging them as there are extra options in cloud's limits that need looked into before removing.
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
Compare the cloud limit schema with Quartz's orgLimit definition and identify the extra options present in the cloud version. Determine whether the APIs can be merged, and document which definition should be retained if they are compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100