Currently, when a develepor registers their Harness CD service into into the IDP catalog utilizing service auto-discovery it only grabs 4 pieces of information. the ability to read add and read a "metadata" block from the actual service object would allow developers to maintain both their IDP catalog entities as well as their actual service in one space, minimizing human toil and creating one source of truth for the service object. custom parsers for the metadata would be an additional ask to allow for seamless updates of the idp catalog without needing to run manual steps every deployment. The same request would be asked for IACM workspaces, allowing for more seamless cross product data fusion.