Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add --ssh-config option to itamae ssh to specify ssh_config #211

Merged
merged 2 commits into from Jul 7, 2016
Merged

Add --ssh-config option to itamae ssh to specify ssh_config #211

merged 2 commits into from Jul 7, 2016

Conversation

koshigoe
Copy link
Contributor

@koshigoe koshigoe commented Apr 30, 2016

I need -F option like SSH to specify alternative ssh_config file.

$ itamae ssh --ssh-config .ssh/development -h devhost -y nodes/web.yml roles/web.rb

@ryotarai
Copy link
Member

ryotarai commented May 2, 2016

--ssh-config option looks good to me, but I think aliasing -F option is not good idea because it can be used for another meaning in the future

@koshigoe
Copy link
Contributor Author

koshigoe commented May 2, 2016

but I think aliasing -F option is not good idea because it can be used for another meaning in the future

Yes, I think so too. But I have no idea.
Can I remove alias? (only --ssh-config)

@koshigoe
Copy link
Contributor Author

koshigoe commented May 2, 2016

MEMO:

At wercker, pass rake spec:unit, but Time-out happened.

Manual page bundle-exec line 1 (press h for help or q to quit)

why opened man page?

Vagrant appears to be running in a Bundler environment. Your 
existing Gemfile will be used. Vagrant will not auto-load any plugins
installed with `vagrant plugin`. Vagrant will autoload any plugins in
the 'plugins' group in your Gemfile. You can force Vagrant to take over
with VAGRANT_FORCE_BUNDLER.

You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.

Bringing machine 'trusty' up with 'digital_ocean' provider...
==> trusty: Droplet is already active
["bundle", "exec", "bin/itamae", "ssh", "-h", "104.236.14.139", "-u", "root", "-p", "22", "-i", "/home/ubuntu/.ssh/id_rsa.vagrant", "-l", "debug", "-j", "spec/integration/recipes/node.json", "spec/integration/recipes/default.rb", "spec/integration/recipes/default2.rb", "spec/integration/recipes/redefine.rb"]
BUNDLE-EXEC(1)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          BUNDLE-EXEC(1)

NAME
       bundle-exec - Execute a command in the context of the bundle

SYNOPSIS
       bundle exec [--keep-file-descriptors] command

DESCRIPTION
       This command executes the command, making all gems specified in the Gemfile(5) available to require in Ruby programs.

       Essentially, if you would normally have run something like rspec spec/my_spec.rb, and you want to use the gems specified in the Gemfile(5) and installed via bundle install(1) bundle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.

       Note that bundle exec does not require that an executable is available on your shell´s $PATH.

OPTIONS
       --keep-file-descriptors
              Exec in Ruby 2.0 began discarding non-standard file descriptors. When this flag is passed, exec will revert to the 1.9 behaviour of passing all file descriptors to the new process.

BUNDLE INSTALL --BINSTUBS
       If you use the --binstubs flag in bundle install(1) bundle-install.1.html, Bundler will automatically create a directory (which defaults to app_root/bin) containing all of the executables available from gems in the bundle.

       After using --binstubs, bin/rspec spec/my_spec.rb is identical to bundle exec rspec spec/my_spec.rb.
 Manual page bundle-exec line 1 (press h for help or q to quit)

@ryotarai
Copy link
Member

ryotarai commented Jul 7, 2016

Sorry for late response. I'm going to merge this. Thank you

@ryotarai ryotarai merged commit 7d79465 into itamae-kitchen:master Jul 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants