You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
pgray64
changed the title
LoadBalancerClient POST unpopulated response object
LoadBalancerClient All single object response routes - unpopulated response object
Sep 2, 2021
LoadBalancerClient
is checking the wrong root element (load_balancers
instead ofload_balancer
) when deserializing the result of POST for creating a new load balancer.This results in the
LoadBalancer
response object never being populatedThis is an issue for all routes that return a single
LoadBalancer
The text was updated successfully, but these errors were encountered: