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

LoadBalancerClient All single object response routes - unpopulated response object #99

Open
pgray64 opened this issue Sep 1, 2021 · 0 comments

Comments

@pgray64
Copy link

pgray64 commented Sep 1, 2021

LoadBalancerClient is checking the wrong root element (load_balancers instead of load_balancer) when deserializing the result of POST for creating a new load balancer.

This results in the LoadBalancer response object never being populated

This is an issue for all routes that return a single LoadBalancer

@pgray64 pgray64 changed the title LoadBalancerClient POST unpopulated response object LoadBalancerClient All single object response routes - unpopulated response object Sep 2, 2021
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

No branches or pull requests

1 participant