-
Notifications
You must be signed in to change notification settings - Fork 85
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
EC2 nodes: internal vs external host names #4
Comments
I've just come across this, looking through lib/chef-rundeck.rb it's returning the fqdn attribute from the node which in ec2 is just the node's hostname rather than the public hostname. A quick (site specific) hack would be to modify this line. A proper fix could be to add another command line switch to chef-rundeck to define what attribute it should use to return the hostname in it's output. Similar to how knife ssh works with -a |
@rmyates We are planning on adding this shortly. |
has this been solved? |
I'll look into it today. On Wednesday, July 16, 2014, JC [email protected] wrote:
Brian Scott - DevOps and Automation Guy, Ruby/Rails Guy, all around Good |
bump |
Thinking about a release this weekend (or maybe Monday), but I don't have a fix for this in flight. I think I can see how I'd implement it but I'm not sure when I'll have the time to do it myself. |
Would love to see this feature as well, specifically being able to define what attribute (i.e. ipaddress) to use for the 'hostname'. |
Take a look at #60. This might be solved already. Just not documented. |
We should document it. Wondering if I should cut a new release. |
Our EC2 nodes show up in RunDeck using the internal names, so we can't connect to them.
The text was updated successfully, but these errors were encountered: