influxdata / influxdata/openapi
api/v2/write has unintuitive ID vs name parameters
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
-
orgIDandorgare both parameters, butorgwill interpret a 16 character hex value as an ID instead of a name, sobadfee0000000001counts as an ID always, never as a name. -
bucketworks like org to prefer an ID and also fall back to trying the value given as a name, but there is no correspondingbucketID. Also this is not documented.
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
Start by reading the OpenAPI specification for the api/v2/write endpoint and inspect how orgID, org, and bucket are defined. Determine the intended distinction between IDs and names, including the missing bucketID behavior, then update the specification and its documentation so the parameter semantics are explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100