Manta VDS Lineage Export to Alation

Manta currently supports VDS lineage export to Alation for Database resource type but any other hierarchy isn't working for us.

We do not intend to have such restriction in place for VDS export of any resource type since it is limiting us from exporting the lineage from Manta to Alation though both sides have an application onboarded as VDS.

As we do not consider an application to have been onboarded completely until the lineage from Manta is exported to Alation, which is the single glass pane for end users who navigate to Manta only when additional lineage information is needed, we need to have this addressed at the earliest in the product OOTB since our onboarding targets along with deliverables to stakeholders are impacted.

Below is the various hierarchies for resources that are being leveraged at Dell for OMD and holds good for VDS export to Alation from Manta that need to accommodate in this case for reference.

--------------------------------------------------------------------------------
Current Manta Supported VDS Hierarchy for Alation Export:
    Custom Database->Database->Schema->Table->Column
    
Required VDS Hierarchies to be supported by Manta for Alation Export:
    Resource[System]->parentLevelNode[Technology]->Custom Database->Database->Schema->Table->Column
    Resource[System]->parentLevelNode[Technology]->Custom Database->Service->API Service->API Object->API Attribute
    Resource[System]->parentLevelNode[Technology]->Custom Databasee->User Application->User Interface->UI Object->UI Attribute
    Resource[System]->parentLevelNode[Technology]->Custom Database->Messaging Service->Topic->Message->Field
    Resource[System]->parentLevelNode[Technology]->Custom Database->Reporting Tool->Report->Report Attribute
    Resource[System]->parentLevelNode[Technology]->Custom Database->File->Field
--------------------------------------------------------------------------------

Kindly let us know if any other information is needed in this regard.