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

change in the strategy to report instances #547

Merged
merged 1 commit into from
Oct 26, 2018

Conversation

lmineiro
Copy link
Contributor

@lmineiro lmineiro commented Oct 25, 2018

This small change seems to be enough to allow reporting instances managed by Elastigroups.

Only AWS can set aws: prefixed tags. Instances created by the Elastigroups don't have the aws:cloudformation:stack-name tag that was used to filter instances.

Pragmatically, I believe that the Name tag contains exactly the same information, although the guarantee that it was created by CloudFormation no longer exists.

If this new approach doesn't sound reasonable, please share the particular uses cases or assumptions where this change will break.

This also changed the instance state filtering to the server side for some micro optimization.

This updates #517

@lmineiro
Copy link
Contributor Author

👍

@jmcs
Copy link
Member

jmcs commented Oct 26, 2018

👍

@jmcs jmcs merged commit c429e24 into master Oct 26, 2018
@jmcs jmcs deleted the implement-instances-for-elastigroups branch October 26, 2018 09:15
jmcs pushed a commit that referenced this pull request Nov 29, 2018
Change in the strategy to report instance status  following the same pragmatic approach as #547
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.

2 participants