Skip to content

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

Open
@pgray64

Description

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

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions