OAS : detailed-logging-is-on attribute is missing under response : schema of /core-model-1-4:control-construct and /v1/list-ltps-and-fcs

[IswaryaaS]

While accessing services like /v1/list-ltps-and-fcs and /core-model-1-4:control-construct , these services responds data of list of operation-client(s) along with the actual data. Here, detailed-logging-is-on is an optional attribute which is present only in operation-client ltp instance of /v1/record-service-request of ExecutionAndTraceLog (*-0-0-1-op-c-0040).

In OAS, under schema specifications of /v1/list-ltps-and-fcs and /core-model-1-4:control-construct, under the path logical-termination-point --> layer-protocol --> operation-client ltp --> operation-client-interface-configuration specification , since the attribute "detailed-logging-is-on" is present only in one-instance among the operation-clients (an optional attribute), can we add it only under properties section(not in required section).

[openBackhaul]

Decision:

• Martin will try to correct the Express framework's oas3/tools module, so it is properly executing the validation of the response, with in 5 working days max.
• Prathiba will change the ApplicationPattern's code in such a way that the /v1/list-ltps-and-fcs service's response will not include the detailed-logging-is-on attribute.
• Thorsten will change the TAC applications' specifications and the applicationPattern in such a way that the detailed-logging-is-on attribute will be part of the properties section (but not the required section!) of the /core-model-1-4:control-construct path.

[openBackhaul]

Update on 13th or May:
In regard to the Specification aspects, this issue has been detailed and will be tracked in the following issues in future:

• detailed-logging-is-on to be added to CC #103
• detailed-logging-is-on to be added to CC RegistryOffice#81
• detailed-logging-is-on to be added to CC TypeApprovalRegister#33
• detailed-logging-is-on to be added to CC ExecutionAndTraceLog#32
• detailed-logging-is-on to be added to CC OamLog#33
• detailed-logging-is-on to be added to CC AdministratorAdministration#27
• detailed-logging-is-on to be added to CC ApplicationLayerTopology#50
• detailed-logging-is-on to be added to CC in OAS OperationKeyManagement#14

[MartinSunal]

Validation is working as described here:
bug-hunters/oas3-tools#43 (comment)
bug-hunters/oas3-tools#43 (comment)

That means we need to change res.end() to be res.json() or res.send() in all application controllers.