Handle GET request for tokens in Meshery .
A documented Meshery . operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Handle GET request for tokens
- GETReads data · UserAPI
meshery.local/api/user/token
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Meshery . operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Meshery . operations
- Handle POST request for Application FilesPOST · changes data
- Handle POST request for tokensPOST · changes data
- Handle POST reqeuest for SchedulesPOST · changes data
- Handle POST request for Application File DeployPOST · changes data
- Handle POST request for load test preferencesPOST · changes data
- Handle POST requests for saving performance profilePOST · changes data
- Handle POST requests for Meshery FiltersPOST · changes data
- Handle POST requests for Kubernetes Context listPOST · changes data
Questions
- Can HumDay handle get request for tokens in Meshery .?
- Yes. This operation is published in Meshery .'s own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Meshery . account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Meshery ..
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Meshery . account.
Where this came from
Read from a published API description for Meshery . at raw.githubusercontent.com/meshery/meshery/master/helpers/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2021-08-23.