backends/none: don't use _ssh_private_key if its corresponding public key hasn't been deployed yet #364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@aszlig I think this should fix #361. I haven't tested it yet but will do that tomorrow.
The boolean attribute
none.sshPublicKeyDeployed
is added to theNoneState and defaults to False. It indicates whether the SSH public key
has been deployed to the target. If it's False the
get_ssh_flags()
function will not set the corresponding private key as the identity.
none.sshPublicKeyDeployed
will be set to True after activating theconfiguration. From then on
get_ssh_flags()
will set the identity to thecorresponding private key allowing nixops to authenticate itself using
the keypair stored in its DB.