/get/rule and /get/rule/:rule endpoints #1
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: florian/hostname-service#1
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
/get/rule and /get/rule:rule endpointsto /get/rule and /get/rule/:rule endpointsActually unbeknownst to me I have implemented this already so....