
Loading…
Use the existing pubkey for the sign in payload #10672
+1
−5
dwfreed
commented
Collaborator
salt-jenkins
commented
Test FAILed.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/1712/
1 check failed
Details
default
Merged build finished.
dwfreed
commented
I've since updated the develop branch on my fork, but I forgot to rebase this branch before opening the pull request. To be fair, when doing pull request builds, Jenkins should be merging the pull request with develop locally, and then initiate the build process. Thanks for merging this :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This page is out of date. Refresh to see the latest.
6
salt/crypt.py
Rather than making a temp file to save out the public key just to read it back in to give to the master for sign in, we can just read the existing public key file that was just created. I should mention that I have not tested this change, as I do not yet have a salt environment up and running. I have looked through the minion sign in flow, and by this point, the keys have already been created if they didn't exist, so removing the call to salt.get_keys() is perfectly safe. I would highly suggest testing starting up a minion, both a fresh one and one that has been running for a while, to verify that both cases don't run into any issues.