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

Refresh ELB listener state #314

Closed
wants to merge 1 commit into from

Conversation

alekstorm
Copy link
Contributor

Allows drift to be updated in the state file.

@pearkes
Copy link
Contributor

pearkes commented Sep 19, 2014

With multiple Listeners, AWS may return in random order on a refresh. We dealt with this a bunch in #87 and so on, and it was eventually fixed in #211.

To handle this properly, we should probably upgrade the ELB resource to use the Schema API. I noticed someone said they were interested in doing that here.

Does that make sense, or am I misunderstanding this?

@mitchellh mitchellh added waiting-response An issue/pull request is waiting for a response from the community and removed waiting-response An issue/pull request is waiting for a response from the community labels Sep 30, 2014
@pearkes pearkes added provider/aws waiting-response An issue/pull request is waiting for a response from the community labels Oct 4, 2014
@mitchellh
Copy link
Contributor

Fixed! Well, totally missed that this was a PR so I just redid the work myself. Whoops.

But, we switched ELB to helper/schema yesterday, so now the ordering will work properly (treated as a set).

@mitchellh mitchellh closed this Oct 10, 2014
@ghost ghost locked and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
provider/aws waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants