Is your feature request related to a problem? Please describe.
Currently, the Agbot API only has routes to get all org secrets, get user secrets and get secrets by node. In order to view all secrets with information about which node or user they belong to, I must loop through all nodes to get secrets for each individual one. This can affect performance as the number of nodes grow.
Describe the solution you'd like.
I would like the route for /org/{org}/secrets to be modified to return a nodeid and userid within each secret object in the list. This way I avoid having to loop through each node and making individual calls for node secrets.
Describe alternatives you've considered
Currently, only solution would be to loop through each node and perform a call to get each nodes secrets.
Is your feature request related to a problem? Please describe.
Currently, the Agbot API only has routes to get all org secrets, get user secrets and get secrets by node. In order to view all secrets with information about which node or user they belong to, I must loop through all nodes to get secrets for each individual one. This can affect performance as the number of nodes grow.
Describe the solution you'd like.
I would like the route for /org/{org}/secrets to be modified to return a
nodeidanduseridwithin each secret object in the list. This way I avoid having to loop through each node and making individual calls for node secrets.Describe alternatives you've considered
Currently, only solution would be to loop through each node and perform a call to get each nodes secrets.
Additional context.
No response