I spent a little time searching through a few repos and docs but was unable to find out the process to get an auth_token for use in Fedora's resultsdb. It's quite possible I'm not looking in the right area but it would be helpful if there was something in the apiary doc or linked to from the README.
auth_token
For some background, we have some Atomic Host QE tests we'd like to start adding as results into resultsdb.
For the curious, where do those tests run?
Can you link us to the source and some execution runs?
@ralph The run in a Jenkins instance and show results to github. You can see the tests (which are done through ansible) here.
FYI the token-auth is not enabled in Fedora's deployment, and so "getting the auth token" for that can not really be documented, even though the code itself is ready(-ish) for that functionality.
Grabbing a client auth (against development instance of Ypsilon) token example code is implemented here: https://pagure.io/taskotron/resultsdb_api/blob/develop/f/tokengetter.py But I suppose that for production, we would be issuing (and allowing) application keys, so this is likely a moot point anyway. Patrick is one of the people with the grand skills and knowledge to explain the details of what would need to happen for us to enable the token auth in production.
Thanks @jskladan. I'll follow up with @puiterwijk and see what we need to do.
Metadata Update from @smilner: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.