mirror of
https://github.com/gravitl/netmaker.git
synced 2025-10-05 16:57:51 +08:00
Added swagger for API docs.
This commit is contained in:
@@ -1,7 +1,13 @@
|
||||
// TODO update to follow actual info.. just set up enough to try out Swagger
|
||||
// Package classification Controller.
|
||||
//Package classification Controller.
|
||||
//
|
||||
// Documentation of the Netmaker API.
|
||||
// API Usage
|
||||
//
|
||||
// Most actions that can be performed via API can be performed via UI. We recommend managing your networks using the official netmaker-ui project. However, Netmaker can also be run without the UI, and all functions can be achieved via API calls. If your use case requires using Netmaker without the UI or you need to do some troubleshooting/advanced configuration, using the API directly may help.
|
||||
//
|
||||
//
|
||||
// Authentication
|
||||
//
|
||||
// API calls must be authenticated via a header of the format -H “Authorization: Bearer <YOUR_SECRET_KEY>” There are two methods to obtain YOUR_SECRET_KEY: 1. Using the masterkey. By default, this value is “secret key,” but you should change this on your instance and keep it secure. This value can be set via env var at startup or in a config file (config/environments/< env >.yaml). See the [general usage](./USAGE.md) documentation for more details. 2. Using a JWT received for a node. This can be retrieved by calling the /api/nodes/<network>/authenticate endpoint, as documented below.
|
||||
//
|
||||
// Schemes: https
|
||||
// BasePath: /
|
||||
@@ -17,9 +23,5 @@
|
||||
// Security:
|
||||
// - oauth
|
||||
//
|
||||
// SecurityDefinitions:
|
||||
// basic:
|
||||
// type: basic
|
||||
//
|
||||
// swagger:meta
|
||||
package controller
|
||||
|
Reference in New Issue
Block a user