Good day fellow uyuni users. I would like to leverage the salt-api that is used by uyuni. Currently the uyuni API does not have a method to list, accept or deny a salt-key. But the salt api does.
I would like to do something like is mentioned here: https://stackoverflow.com/questions/19067341/using-salt-api-to-call-salt-key...
I have inspected the salt-api that is setup on uyuni and it is currently set up to only listen on the loopback interface which is easy to change. The next problem I have seems to be that the file based admin authentication does not match the admin account that I used to set up uyuni. I'm wondering if it is stored somewhere in the database for internal communication with the salt-api?
Is there a safe way to get/set the password without disrupting internal comms with the api? Or is there a way to set up a second salt-api on the same box? I'm not a saltstack guru so I would love it if someone could point me in the right direction.
On 04/08/2021 02.33, Jesse Harris wrote:
Or is there a way to set up a second salt-api on the same box? I'm not a saltstack guru so I would love it if someone could point me in the right direction.
Yes, you can define multiple salt netapi endpoints for the same salt-master, and that is the recommended way not to interfere with the endpoint used and configured by Uyuni.
I'd suggest to set up an additional tornado endpoint: https://docs.saltproject.io/en/latest/ref/netapi/all/salt.netapi.rest_tornad...
Regards, -- Silvio Moioli SUSE Manager Development Team