pi-hole requires initial auth with app password using POST to get token before api call for version info

[durango99]

I wanted to try out Argus and wasn't sure how to create a service with pi-hole version check. https://docs.pi-hole.net/api/auth/ shows a 2 part process - 1] POST to /api/auth with the password in the header. 2] take the response code that has the session id and then 3] GET http://pi.hole/api/info/version with the session id.

Can this be done all in the yaml file? or would I use the command option to run a shell script to get the session ID and then pass it to the pi-hole yaml entry?

Thanks!

[JosephKav]

Hi, I'm not sure Argus is able to continuously monitor Pi-Hole if it requires you to frequently get a token for API requests to retrieve the version :/. You'd need metrics or something that expose the hosted version with no/consistent auth. You may just have to do it manual for now?

[durango99]

Hi Joseph, Thanks for the response. I've gone ahead and set up a manual for now, yes. I was hoping for some function in Argus that could handle a "double" API request 1] initial POST with password/key, regex to get the token/sid and 2] then use the generated token/sid to do the actual API call. Otherwise, another nice addition would be to have a command: [] option under the deployed_version: (like we have under latest_version:) where I could run a bash script to do the initial POST outside of argus and get the value of the token/sid to use as a variable for the API call.

I'm thinking if neither are feasible, I'll just do a cron that runs the bash script at intervals and have some webservice that argus uses as the url for deployed_version to get the API version. That seems a bit of work to handle these type of API situations.

Thanks