FlowsourceConnection Name is missing

[ss1034]

Module: flowService

self.flowSourceConnection['connectionSpec']['name'] is always returning null value - this was working in previous version inside flowService init()

Code sample:
flowMgr = flowservice.FlowManager(flow.get('flow_id'))
flowsrc_conn = flowMgr.flowSourceConnection
src_conn_param = flowsrc_conn['params']
if 'connectionSpec' in flowsrc_conn:
src_name = flowsrc_conn['connectionSpec'].get('name')

[pitchmuc]

Hello @ss1034
What the FlowManager is doing is, based on the flowId used, it returns all related artefacts, such as SourceConnection and TargetConnection and stores them into the variable you are using (flowMgr.flowSourceConnection in your case).
I am not sure how the Flow API changed, the aepp wrapper (and subsequent modules and classes) are based on the API response of the AEP API, in that case, the Flow Service API.
If the Flow Service API changes its response, it cannot solve the issue.
I have checked and it is not returning the ConnectionSpec name as you are explaining here.

I would recommend to open a ticket to Customer Care and request a roll back or an explanation or a feature enhancement.

Knowing the Adobe engineering service, this will either take a long time or will not be considered... It may not be an issue in their eyes.
There are different ways to accomplish that though.

In your example, you can realize the following:

flowMgr = flowservice.FlowManager(flow.get('flow_id'))
connSpec = flowMgr .getConnectionSpec()
connSpecName = connSpec.get('items',[{}])[0].get('name')

I will close the issue next week as this is not an aepp issue but probably an API design change from Flow Service that I cannot fix as not part of this department and service.

Sorry for the inconvenience.

[ss1034]

Thank you @pitchmuc for the swift response. I wanted to highlight a change in behaviour compared to previous version rather than an aepp bug. However, I understand that if the underlying API response has somehow altered, the wrapper itself cannot know and should not resolve.

I appreciate the alternate resolution and your time supporting the wrapper!

Thank you,
Supratim

[passionworkeer]

This bug might be related to: 1) API response structure changed - check if connectionSpec.name is now in a different field, 2) Verify the API endpoint returns the name field - inspect raw API response, 3) Check if this is a regression from a recent update by comparing with previous version. Could you share the API response payload to confirm the field structure?