Hi Will, As an alternative workaround for this, you can go to the SSH Key page, download the public key, create a custom script of 'echo "public-key-hash-here" >> /root/.ssh/authorized_keys' and execute on the instance. That should inject the key and then SSH login should work as expected. SSH Key deployment on HostInit event for Azure has been included in the recent release of Scalr Enterprise Edition 6.0.5.
Many thanks, Wm. Marc O'Brien Scalr Technical Support On Thursday, June 2, 2016 at 9:17:02 AM UTC-6, William White wrote: > > Once you have the images sync'd up you'll launch a base image and attempt > to ssh to the new box. You'll bang your head on ssh keys for a while until > you find this entry that talks about ssh keys not being managed by Scalr at > this time. > > https://groups.google.com/forum/#!topic/scalr-discuss/poQjoqci14g > > Thanks, > > WW > > On Tuesday, May 31, 2016 at 10:09:07 AM UTC-5, William White wrote: >> >> Looks like this has already been answered: >> >> https://github.com/Scalr/scalr/issues/71 >> >> Thanks, >> >> WW >> >> On Tuesday, May 31, 2016 at 9:42:17 AM UTC-5, William White wrote: >>> >>> When adding a new role I click "Start Building" and receive the >>> following error: >>> >>> Azure error. The api-version '2015-05-01-preview' is invalid. The >>> supported versions are >>> '2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'. >>> >>> I'm guessing this is a response from Azure. Is this a configuration >>> that I need to change somewhere? >>> >>> Thanks, >>> >>> WW >>> >> -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
