Closed mohierf closed 6 years ago
@mohierf information failures are available in DEBUG mode of App.
For command buttons (ACK and DOWNTIME), I left them for the moment active because the actionacknowledge
and actiondowntime
endpoints of the backend API are still valid.
If you think I have to make them inactive if there is no Web Service, I can.
It may be more logical to disable the buttons IF a Web Service URI is set. If WS URI is set, it means, use the WS Alignak module ... and if it is not available, no commands may be raised from the App.
Looks more logical, no ?
I did not see WS integration like that. I thought the backend API was the main connection with the backend... and WS can add some features or better access.
Ok, if you think it's more logical this way. So, just for the actions ?
Or should the WS be used for all (in the long run) queries if it is enabled (because, some endpoints are still missing...) ?
The WS will be the main Alignak (+ backend) API ... the backend is only an internal data model and the WS aims to expose. the idea is to hide the backend behind the WS :)
So:
Do you agree @mohierf ?
Yes
Done.
When the connection to the Alignak WS fails, the user do not have any information about the connection failure. Raising an alert may be interesting ?
And why does this connection fail ? My backend username/password is valid and thus the WS should be Log:
What is the app behavior when the WS is not available? The commands button are still active whereas they should not IMHO...