Add missing Cloud Routes keys
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- json, openapi, yaml
- Domain
- api
Research direction
The Cloud Routes schema lives in contracts/cloud.yml, so start there and find where the existing route keys are declared. Add invocableScripts as a string URI and telegraf as an object with a plugins URI property, matching the surrounding entries. Done when the spec includes both keys and GET /api/v2 keys match the payload shown in the issue.
Written by the indexing model from the issue text.
Description
2. Cloud Routes schema is missing invocableScripts and telegraf
Problem
GET /api/v2 on Cloud 2 returns two keys that contracts/cloud.yml doesn't list in the Routes schema:
{
"invocableScripts": "/api/v2/scripts",
"telegraf": { "plugins": "/api/v2/telegraf/plugins" }
}
Both routes are live: GET /api/v2/scripts and GET /api/v2/telegraf/plugins return 200.
Verification
curl -s "$INFLUX_HOST/api/v2" -H "Authorization: Token $INFLUX_TOKEN" | jq -c 'keys'
Suggested solution
Add invocableScripts (string, URI) and telegraf (an object with a plugins URI property) to the Cloud Routes schema.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from influxdata/openapi
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
influxdata/openapi#657 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
influxdata/openapi#653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
influxdata/openapi#240 ·
-
Update /ready and /health schemas for v2.10Possibly taken @devanbenz claimed this 1 day ago. Open
influxdata/openapi#659 · 1 comment · 2 assignees ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
influxdata/openapi#636 ·
All issues in influxdata/openapi
Similar issues
-
command: monitor command: update info: steamcmd reproducible: always severity: medium type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
GameServerManagers/LinuxGSM#4997 ·
Maintainers usually reply within 1 day
-
area:space-accuracy good first issue track:data
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Sara-Managed-Projects/space-radar#886 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zerocracy/judges-action#2733 ·
Maintainers usually reply within 8 days
-
[Nginx] Warning: duplicate extension "wasm" in nextcloud.confPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 74/100
YunoHost-Apps/nextcloud_ynh#916 ·
Maintainers usually reply within 1 day
-
dependencies feature github_actions good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
wemake-services/wemake-django-template#3149 ·
Maintainers usually reply within 1 day