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

Fix for EC2.Waiter.InstanceExists raising JMESPathTypeError #907

Closed
wants to merge 1 commit into from
Closed

Fix for EC2.Waiter.InstanceExists raising JMESPathTypeError #907

wants to merge 1 commit into from

Conversation

nicholasbishop
Copy link
Contributor

Reverted the "success" acceptor for that waiter to an earlier version
that checks only the response code, not the response body.

Added a unit test that reproduces the issue and passes with the
change to the JSON file.

Bug: #906

Reverted the "success" acceptor for that waiter to an earlier version
that checks only the response code, not the response body.

Added a unit test that reproduces the issue and passes with the
change to the JSON file.

Bug: #906
@@ -7,9 +7,8 @@
"operation": "DescribeInstances",
"acceptors": [
{
"matcher": "path",
"expected": true,
"argument": "length(Reservations[]) > `0`",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this was added because it's possible to get an empty reservations list even if you specify an instance id in some cases. I think we'll just need to modify the waiter code to handle this case appropriately.

@jamesls
Copy link
Member

jamesls commented May 12, 2016

I pulled in your PR and updated the code to only search non error responses. Closing in favor of #917

Thanks for the pull request.

@jamesls jamesls closed this May 12, 2016
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