api-reference: Legacy Authorizations - delete a legacy authorization
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- api, documentation
Research direction
The issue has no body, named files, tests, or entry points. Start by locating the Legacy Authorizations section in the repository's OpenAPI specification and determine which delete-authorization reference is intended; done means the requested legacy authorization reference is removed and the specification remains valid.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. 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 Routes.yml for backup, restore, labels, notificationRules, notificationEndpoints, scrapers, swagger, checks, plugins, delete, readyMay be free again @devanbenz claimed this 142 days ago, and no pull request is open. Openbug
influxdata/openapi#654 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
influxdata/openapi#636 ·
All issues in influxdata/openapi
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
alunduil/alunduil-infrastructure#629 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
duckdb/duckdb-skills#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
YosysHQ/oss-cad-suite-build#216 ·