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
Currently discovery connections are shaped around AWS and vSphere connections. The DiscoveryConnection class and Connection#list_discovery_connections method should be updated to only return the relevant values for each connection type.
DHCP connections over Microsoft DHCP and a directory watcher for example do not include a port value, but do include an engine ID (which no other discovery connections use today).
The text was updated successfully, but these errors were encountered:
Hmm looking into this, I think there is something fishy about the XML response currently. We're showing an engine ID for non-DHCP connections, which as you said is not used that way. This seems like it would not validate against the 1.2 API schema. Edit: The schema has been updated for the optional fields, but I feel like there would still be problems for some other clients consuming it.
Currently discovery connections are shaped around AWS and vSphere connections. The
DiscoveryConnection
class andConnection#list_discovery_connections
method should be updated to only return the relevant values for each connection type.DHCP connections over Microsoft DHCP and a directory watcher for example do not include a port value, but do include an engine ID (which no other discovery connections use today).
The text was updated successfully, but these errors were encountered: