Salt: Azure: ssh_password required in profile, ssh_keyfile not used

[danielgblanco]

It's not possible to use a key file to deploy Salt on a minion. Only SSH password access is enabled, and the creation of an instance fails if ssh_password is not present. It'd be good to have an ssh_keyfile like for other cloud providers.

Also, ssh_username, ssh_password and media_link need to be in the profile, and can't be taken from the provider configuration. Is this a design decision? I'd like to have the same credentials for all instances and declare it in the provider configuration, in the same way it's done for EC2.

Many thanks.

[justinta]

@danielgblanco I want to say it is possible. I'll look into it and get back to you.

[techhat]

It is possible, but kind of a pain. @jtand, ping me if you're interested in working on this. I've already gotten part of it done.

[justinta]

@techhat Yeah, lets get together. I'd like to see what you have so far.

[danielgblanco]

Any updates on this? Thanks.

[danielgblanco]

Hi,

This issue is in "Info needed" state... Is there anything I can do?

[rallytime]

Thanks for the bump here @danielgblanco. Looks like we just never got back to it.

@jtand or @techhat Did you guys get a chance to look at this one?

[mitar]

I also just tried to use Salt to deploy to Azure, but realized this problem with the password. SSH key would be really great to have.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.