A custom fact was the way to go.
My fact was hanging because I hadn't supplied '-n' to the ssh invocation.
Apologies for the noise.
Mark
On Monday, March 18, 2013 2:19:14 PM UTC, mark.a...@thebbgroup.org wrote:
>
> Hi
>
> I'm using vagrant/puppet to create development environments for our team.
Solution found here:
https://github.com/mitchellh/vagrant/issues/603#issuecomment-13791117
All I needed was to add '-n' to the ssh invocation and it works perfectly.
On Mon, Mar 18, 2013 at 3:45 PM, Mark Allison
wrote:
> On Mon, Mar 18, 2013 at 3:42 PM, llowder wrote:
>
&g
On Mon, Mar 18, 2013 at 3:42 PM, llowder wrote:
> Are you running facter and puppet as the same user?
>
I believe so. In testing I run as user root. During 'puppet apply' (via
'vagrant provision') I believe facter is run as root. I checked this by
changing my command to /bin/whoami. That return
Hi
I have the following custom fact:
require 'facter'
Facter.add("chat_remote_port", :timeout => 5) do
setcode do
Facter::Util::Resolution.exec('/usr/bin/ssh -o StrictHostKeyChecking=no
-i /vagrant/fabfile/deployment/keys/id_rsa u...@example.com \'for port in
12321 12322 12323 12324 12325
Hi
I'm using vagrant/puppet to create development environments for our team.
Part of the set-up is creating a reverse ssh tunnel between the vagrant box
and a central server. I'd like to be able to automatically allocate that
port number when 'provision' is run and use it in a couple of resourc
