Team,

We currently rely on a custom script to dynamically retrieve service manifest details for Helm and Kubernetes‑based deployments. However, the existing Harness expression:

"<+manifestConfig.primaryManifestId>" only returns the manifest identifier for Helm‑based services and is not supported for Kubernetes or other service types.

To streamline our deployment workflow, we need a reliable and consistent way to dynamically retrieve both the manifest ID and manifest name directly from the service - without requiring prior knowledge of the manifest identifier.

Enabling this capability would:

• Significantly reduce manual overhead and configuration effort

• Improve the accuracy and reliability of scripts referencing manifest details

This improvement would greatly optimize our deployment process and we kindly request that this feature be prioritized, as it will have a meaningful impact on operational efficiency across multiple service types.