-
Notifications
You must be signed in to change notification settings - Fork 45
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
Only one instance from ASG appears if EC2 name tag used as name #101
Comments
Did you get this to work @bashton-ajenkins ? I tried setting |
yeah, the
And then just searching by nametag. IE:
/shrug |
Hey guys, the best solution I found for this is to just use the instance ID as the name and use the instance name as a tag (this is the solution I mention in the original post). This allows you to target the instances by the tag name to run commands against all instances with that name or if you want to run on an individual instance you would need to just target it by it's ID |
I also have this issue. As noted above i have made changes to list nodes with their instance ID but this is really unreadable from a UI point of view. It was documented that you could append a value like so: |
I thought this was a bug too, but I think it's just sensitive. I used this in mine: nodename.selector=tags/Name+' ('+privateIpAddress+')';username.default=; Notice the nodename.selector is first on the params line, and also could not have a space between the semi-colon and username.default property. And it appears to be working now. |
By default the plugin will only list one instance of a group of instances if their EC2 name tag is the same.
To work around this I have had to set this as the mapping parameter:
However it results in the Nodes list being harder to navigate unless you use the tags to filter (as you just have a list of ec2 instance IDs).
The text was updated successfully, but these errors were encountered: