Avoid connection with AWS for SSH shell vagrant provision
jacace opened this issue · 2 comments
Hello colleagues,
For some reason the command below connects with AWS to execute a SSH direct command:
vagrant provision --provision-with shell
I believe this is to retrieve the public hostname.
I believe this is not really necessary since the hostname could be retrieved from the Vagrantfile param config.vm.hostname or even from a input command line param e.g.:
vagrant provision --provision-with shell --hostname=abc
This has the benefits below:
- Faster command execution.
- Connectivity to existing instances not created with vagrant.
- Not need to know the AWS access and secret keys since no connectivity to AWS would be needed.
I did a quick test unsuccessfully (due to the fact that connection information it seems to be all around the place) by commenting out the ruby source code line where the AWS creds are tested in file .vagrant.d\gems\2.4.4\gems\fog-aws-2.0.1\lib\fog\aws\compute.rb as follows:
@host = "host name or IP address"
#Fog::AWS.validate_region!(@region, @host)
But it later breaks in line 103 in function of file \.vagrant.d\gems\2.4.4\gems\excon-0.62.0\lib\excon\socket.rb when it tried to translate the hostname to IP address info
addrinfo = ::Socket.getaddrinfo(*args)
So having that said, may I ask?
- Could an AWS-less vagrant provision be considered for a potential new feature?
- Whether the answer to the previous ask is yes or not, how can currently hack it to be able to provide the hostname to avoud any connectivity with AWS?
Thanks,
Javier Caceres
Just to mention that another benefit (if request here is possible) is that one could give a user a local username and password of an existing VM instead of sharing keys, etc.