/get/rule and /get/rule/:rule endpoints #1

Closed
opened 2024-01-22 10:30:06 +01:00 by florian · 1 comment
Owner

Idea

A dynamic API consumer like a web interface needs a way to know about existing rules and needs a way to find their input parameters. We could provide two API endpoints that allow this easily. This could help writing client applications like a Webinterface

Discussion

In our demo powershell example we parse this directly from the swagger documentation which is not the worst way of doing that. Thats what it is there for - other than making a nice looking human readable UI.

### Idea A dynamic API consumer like a web interface needs a way to know about existing rules and needs a way to find their input parameters. We could provide two API endpoints that allow this easily. This could help writing client applications like a Webinterface ### Discussion In our demo powershell example we parse this directly from the swagger documentation which is not the worst way of doing that. Thats what it is there for - other than making a nice looking human readable UI.
florian added the
Kind/Feature
Status
Need More Info
labels 2024-01-22 10:30:06 +01:00
florian changed title from /get/rule and /get/rule:rule endpoints to /get/rule and /get/rule/:rule endpoints 2024-01-22 10:30:22 +01:00
florian added
Reviewed
Duplicate
and removed
Status
Need More Info
labels 2024-02-06 21:19:29 +01:00
Author
Owner

Actually unbeknownst to me I have implemented this already so....

Actually unbeknownst to me I have implemented this already so....
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: florian/hostname-service#1
No description provided.