juju2beta10 websockets api: Inconsistency in lowercasing of endpoints in deltas versus servers key in login response

Bug #1597372 reported by Chad Smith
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Tim Penhey

Bug Description

Juj2ubeta10 underwent lower-casing of most websockets api parameters, as a result there is now an inconsistency in how machine change deltas list of 'Addresses' are represented versus the list of 'servers' in the login response. Addresses uses camelcase Scope, Type, SpaceName, Value, etc. Login response 'servers' uses lowercase scope, type, port value.

As an api consumer, we have been using the same logic to parse 'Addresses' from watcher deltas response and 'servers' list from the Login response. It seems beta10 renames cause divergence in the parameter names in these responses adding to complexity when parsing such responses.

tags: removed: kanban-cross-team
Chad Smith (chad.smith)
description: updated
Tim Penhey (thumper)
Changed in juju-core:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Tim Penhey (thumper)
milestone: none → 2.0-beta11
Tim Penhey (thumper)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta11 → none
milestone: none → 2.0-beta11
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.