Automate Meshery .

What Meshery . is

the purpose of this application is to provide an application that is using plain go code to define an API This should demonstrate all the possible comment annotations that are available to turn go code into a fully compliant swagger 2.0 spec

API host: meshery.local

What HumDay can do in Meshery .

32 documented operations change something in Meshery ..

• POSTHandle POST request for Application Files/api/application/
• POSTHandle POST request for tokens/api/user/token
• POSTHandle POST reqeuest for Schedules/api/user/schedules
• POSTHandle POST request for Application File Deploy/api/application/deploy
• POSTHandle POST request for load test preferences/api/user/prefs/perf
• POSTHandle POST requests for saving performance profile/api/user/performance/profiles
• POSTHandle POST requests for Meshery Filters/api/filter
• POSTHandle POST requests for Kubernetes Context list/api/system/kubernetes/contexts
• POSTHandle POST requests for patterns/api/pattern
• POSTHandle GET for User Load Test Preferences/api/user/prefs
• POSTHandle POST request for Pattern Deploy/api/pattern/deploy
• POSTHandle POST request for Kubernetes Config/api/system/kubernetes
• DELETEHandle DELETE request for Application File Deploy/api/application/deploy
• DELETEHandle Delete for a Meshery Application File/api/application/{id}
• DELETEHandle DELETE request for load test preferences/api/user/prefs/perf
• POSTHandle POST requests to persist adapter config/api/system/adapter/manage
• POSTHandle POST requests for Adapter Operations/api/system/adapter/operation
• POSTHandle POST request for Prometheus board/api/telemetry/metrics/boards
• POSTHandle POST for Prometheus configuration/api/telemetry/metrics/config
• POSTHandle POST request for Prometheus board import/api/telemetry/metrics/board_import
• DELETEHandle DELETE reqeuest for Schedules/api/user/schedules/{id}
• POSTHandle POST request for Grafana boards/api/telemetry/metrics/grafana/boards
• POSTHandle POST request for Grafana configuration/api/telemetry/metrics/grafana/config
• DELETEHandle DELETE request for Pattern Deploy/api/pattern/deploy
• DELETEHandle DELETE request for Kubernetes Config/api/system/kubernetes
• POSTHandles registering OMA objects/api/oam/{type}
• DELETEHandle Delete requests for performance profiles/api/user/performance/profiles/{id}
• DELETEHandle Delete for a Meshery Filter/api/filter/{id}
• DELETEHandle Delete for a Meshery Pattern/api/pattern/{id}
• DELETEHandle DELETE requests to delete adapter config/api/system/adapter/manage
• DELETEHandle DELETE for Prometheus configuration/api/telemetry/metrics/config
• DELETEHandle DELETE request for Grafana configuration/api/telemetry/metrics/grafana/config

What HumDay can read from Meshery .

These are the operations a schedule or a trigger can watch.

• GETHandle GET request for list of providers/api/providers
• GETHandle GET request for Application Files/api/application/
• GETHandlers GET request for User login/api/user/login
• GETHandle GET for User Load Test Preferences/api/user/prefs
• GETHandle GET request for tokens/api/user/token
• GETHandlers GET request for User logout/api/user/logout
• GETHandle GET reqeuest for Schedules/api/user/schedules
• GETHandle GET request to provider UI/provider
• GETHandle GET request for load test preferences/api/user/prefs/perf
• GETHandle GET request for Prometheus Query/api/telemetry/metrics/query
• GETHandle GET requests for performance profiles/api/user/performance/profiles
• GETHandle GET request for all filters/api/filter
• GETHandle GET request for patterns/api/pattern
• GETHandle GET request for the choice of provider/api/provider
• GETHandle GET request for filter file with given id/api/filter/file/{id}
• GETHandle GET reqeuest for Schedules/api/user/schedules/{id}
• GETHandle GET request for config sync/api/system/sync
• GETHandle GET request for Grafana queries/api/telemetry/metrics/grafana/query
• GETHandle GET request to run a test/api/perf/profile
• GETHandles GET requests for performance results/api/user/performance/profiles/results
• GETHandle GET request for system/server version/api/system/version
• GETHandle GET request for adapters/api/system/adapters
• GETHandle GET request for React Components/api/provider/extension
• GETHandle GET requests for Provider/api/provider/capabilities
• GETHandles the get requests for the OAM objects/api/oam/{type}
• GETHandle GET requests for performance results of a profile/api/user/performance/profiles/{id}
• GETHandle GET request for a Meshery Filter/api/filter/{id}
• GETHandle GET for a Meshery Pattern/api/pattern/{id}
• GETHandle GET request for Meshery Application with the given id/api/application/{id}
• GETHandles GET requests for perf results/api/perf/profile/result
• GETHandle GET request for Kubernetes ping/api/system/kubernetes/ping
• GETHandle GET request for Prometheus Ping/api/telemetry/metrics/ping
• GETHandle GET request for mesh-sync grafana/api/system/meshsync/grafana
• GETHandle GET for Prometheus configuration/api/telemetry/metrics/config
• GETHandle GET request for fetching prometheus/api/system/meshsync/prometheus
• GETHandle GET request to run a performance test/api/user/performance/profiles/{id}/run
• GETHandle GET request for Prometheus static board/api/telemetry/metrics/static-board
• GETHandle GET request for results of a profile/api/user/performance/profiles/{id}/results
• GETHandle GET request for Grafana ping/api/telemetry/metrics/grafana/ping
• GETHandle GET request for Grafana/api/telemetry/metrics/grafana/scan
• GETHandle GET request for Grafana boards/api/telemetry/metrics/grafana/boards
• GETHandle GET request for Grafana configuration/api/telemetry/metrics/grafana/config
• GETHandles GET requests for perf result/api/perf/profile/result/{id}

How automating Meshery . works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Meshery . account.
4. Grant access, then go live. You approve the specific Meshery . operations it may use — and only those.

Automate Meshery . with these

• Cloudflare3122 operations
• Netboxdemo NetBox386 operations
• Linode342 operations
• Clever Cloud324 operations
• DRACOON276 operations
• Box Platform258 operations
• Netlify's documentation120 operations
• Ritc66 operations
• Microsoft Custom Vision Training Client48 operations
• Turbinelabs Turbine Labs44 operations
• Ably Control22 operations
• Ably Platform22 operations

Categories

• Cloud

Questions about Meshery . automation

Can HumDay connect to Meshery .?

Yes. HumDay reads Meshery .'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 75 operations are documented.

Do I need to write code to automate Meshery .?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Meshery . account.

What can HumDay do in Meshery .?

32 of the 75 documented operations change something in Meshery ., and 43 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Meshery . account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Meshery . is held behind that approval.

Where this came from

The operations above are read from a published API description for Meshery . at raw.githubusercontent.com/meshery/meshery/master/helpers/swagger.yaml. Descriptions are the provider’s own words, not ours. Last published 2021-08-23.