You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to have an interactive mode people can use to navigate the APIs a bit more easily.
For example, if we wanted to check role for a user, this would ask you what kind of task you'd want to perform (like information about a user), and then would prompt you for the needed arguments.
This will be addressed when we have usage of this tool and see if it's necessary (are there enough pain points to justify the effort needed to develop this?)
I think this could be done fairly simply using a decision tree, the new --filter flag, and building a filter term:
(PSUEDO behavior and output)
Getting data (1), or updating (2)? 1 (behind the scenes, we add a filter: "get"..... or "set" for 2)
Regarding (choose 1)?
User (1)
Group (2)
Compute Resource(3)
Experiment(4): 2 (filters: get, resource)
etc...
I could (quickly) add a feature to the filter flag to filter by multiple terms, which can filter either by "contains either term" or "contains all terms"
In which case, the end result can run a workload (interactive_response, or something):
relevant_endpoints: ferry_cli --filter=get,resource -le (return subparser array before printing)
print("These might be the endpoints you are looking for")
for ep in relevant_endpoints:
print(ep.description)
ferry_cli -ep {endpoint name}
Activity
LTrestka commentedon Jan 14, 2024
I think this could be done fairly simply using a decision tree, the new --filter flag, and building a filter term:
(PSUEDO behavior and output)
Getting data (1), or updating (2)? 1 (behind the scenes, we add a filter: "get"..... or "set" for 2)
Regarding (choose 1)?
User (1)
Group (2)
Compute Resource(3)
Experiment(4): 2 (filters: get, resource)
etc...
I could (quickly) add a feature to the filter flag to filter by multiple terms, which can filter either by "contains either term" or "contains all terms"
In which case, the end result can run a workload (interactive_response, or something):
relevant_endpoints: ferry_cli --filter=get,resource -le (return subparser array before printing)
print("These might be the endpoints you are looking for")
for ep in relevant_endpoints:
print(ep.description)
ferry_cli -ep {endpoint name}