1
0
Fork 0
mirror of https://git.rwth-aachen.de/acs/public/villas/node/ synced 2025-03-09 00:00:00 +01:00
VILLASnode/doc/openapi
pipeacosta e9be876d36 Added the configuration schema for the api_client node type
Signed-off-by: pipeacosta <pipeacosta@gmail.com>
2023-08-25 08:18:20 +00:00
..
components Added the configuration schema for the api_client node type 2023-08-25 08:18:20 +00:00
paths update OpenAPI spec 2022-03-28 16:21:41 +02:00
openapi.yaml update Steffens mail address 2022-12-16 23:44:07 +01:00
README.md add new openapi spec 2021-11-18 12:10:36 +01:00

The openapi folder

This folder contains your entrypoint openapi.yaml.

That file contains references to the entire API definition.

Here are some sections to pay attention to:

  • Top-level description: this accepts markdown, and Redoc and Redocly API Reference will render it at the top of the docs. Consider maintaining your markdown in a separate file and embedding it. Note to Redoc community edition users, the special tags are only available to the Redocly API Reference users, but you can still embed markdown.
  • Security schemes: you will define the scheme(s) your API uses for security (eg OAuth2, API Key, etc...). The security schemes are used by the Redocly API Reference "Try It" API console feature.
  • Paths: this defines each endpoint. A path can have one operation per http method.
  • Tags: it's a good idea to organize each operation. Each tag can have a description. The description is used as a section description within the reference docs.
  • Servers: a list of your servers, each with a URL.