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
In the postman collection there is a way to get a list of all commands. The path in the product is typically servername/api/commands. With the 21.0 release, this no longer works. Instead a request for that path returns this response:
{
"message": "No HTTP resource was found that matches the request URI 'https://SERVERNAME.EXAMPLE.COM/api/commands/'.",
"messageDetail": "No action was found on the controller 'Commands' that matches the request."
}
The list of commands was very helpful so it would be best to restore it in the product, but if not, it should be removed from the collection or provide an alternative.
The text was updated successfully, but these errors were encountered:
It does look like GetCommands is no longer available, so we may be updating the Postman collections to reflect that. We now provide Swagger UI documentation though that you could use. You should be able to navigate to ../swagger/ui to view available commands.
Thanks Joe. The Swagger/UI is awkward to use in the 21 release (due to the unnecessary paging) and a poor replacement for the very convenient list of all commands in one place. Compared to 20 these are disappointing steps backward.
In the postman collection there is a way to get a list of all commands. The path in the product is typically servername/api/commands. With the 21.0 release, this no longer works. Instead a request for that path returns this response:
The list of commands was very helpful so it would be best to restore it in the product, but if not, it should be removed from the collection or provide an alternative.
The text was updated successfully, but these errors were encountered: