|
Post by tophercantrell on Feb 2, 2018 15:02:14 GMT
Many of the Manager.json versions e.g. Manager.v1_0_5.json have a definition for "ManagerService". The definition is always empty and never referenced anywhere else in the schema. Is this for future expansion?
|
|
|
Post by mraineri on Feb 2, 2018 17:47:50 GMT
This appears to be an artifact of the "ManagerService" ComplexType definition found in "Manager_v1.xml". That definition is an abstract type, and it gets leveraged by things like the "SerialConsole", "CommandShell", and "GraphicalConsole" definitions.
For example:
<ComplexType Name="SerialConsole" BaseType="Manager.v1_0_0.ManagerService"> <Annotation Term="OData.AdditionalProperties" Bool="false"/> <Annotation Term="OData.Description" String="Information about a Serial Console service provided by a manager."/> <Annotation Term="OData.LongDescription" String="This type shall describe a Serial Console service of a manager."/> <Property Name="ConnectTypesSupported" Type="Collection(Manager.v1_0_0.SerialConnectTypesSupported)" Nullable="false"> <Annotation Term="OData.Permissions" EnumMember="OData.Permission/Read"/> <Annotation Term="OData.Description" String="This object is used to enumerate the Serial Console connection types allowed by the implementation."/> <Annotation Term="OData.LongDescription" String="The value of ConnectTypesSupported shall be an array of the enumerations provided here. SSH shall be included if the Secure Shell (SSH) protocol is supported. Telnet shall be included if the Telnet protocol is supported. IPMI shall be included if the IPMI (Serial-over-LAN) protocol is supported."/> </Property> </ComplexType> We'll look into cleaning this up in the JSON conversion so we don't produce that empty artifact.
|
|
|
Post by tophercantrell on Feb 6, 2018 14:53:34 GMT
Thank you so much! You are providing great service!
|
|