-
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
Make the Attribute Reported as Hostname Configurable #60
Comments
Hm, after reading the code I think this is already possible by setting the |
A very basic example of a project configuration would be: {
"URL_PATH": {
"hostname": "CUSTOM_HOSTNAME_ATTRIBUTE",
"pattern": "*:*"
}
} Then chef-rundeck serves the node information with your custom hostname at |
How would one reference an attribute such as ec2::public_hostname ? I have tried a few different formats / syntaxes but not getting anything |
To answer my own question... You can't without modifying the code at Line 229 Change to: n['hostname'] = get_custom_attr(node, hostname.split('.')) |
It would be nice if the attribute which is reported as the
hostname
to Rundeck was configurable. So that Rundeck can use any of the attributes returned by Chef to connect to the VMs.For example to use the nodename instead of the hostname. Not every network setup let's you connect to the VMs using the hostname of the VM.
This would also help with the tickets #59 and #4.
The text was updated successfully, but these errors were encountered: