Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add operations tagging for more intentional grouping of APIs #182649

Closed
Tracked by #180056
jloleysens opened this issue May 6, 2024 · 1 comment · Fixed by #184320
Closed
Tracked by #180056

Add operations tagging for more intentional grouping of APIs #182649

jloleysens opened this issue May 6, 2024 · 1 comment · Fixed by #184320
Labels
Feature:OAS Work or issues related to Core-provided mechanisms for generating OAS Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@jloleysens
Copy link
Contributor

jloleysens commented May 6, 2024

Best practice is to provide some way to intentionally tag an API (i.e. GET /api/cool-object) as belonging to a group: Cool object.

Bonus, we should provide a way to describe these top-level tags. This could be done in a follow up PR to providing support for tags as such.

@botelastic botelastic bot added the needs-team Issues missing a team label label May 6, 2024
@jloleysens jloleysens added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc and removed needs-team Issues missing a team label labels May 6, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@jloleysens jloleysens added the Feature:OAS Work or issues related to Core-provided mechanisms for generating OAS label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:OAS Work or issues related to Core-provided mechanisms for generating OAS Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants