Bug: Kargo Cannot Render Manifests with Same Name

[BenjaminNeale-Heritage]

Checklist

• I've searched the issue queue to verify this is not a duplicate bug report.
• I've included steps to reproduce the bug.
• I've pasted the output of kargo version.
• I've pasted logs, if applicable.

Description

If there are multiple manifests of the same kind with the same name but in different namespaces then Kargo Render will only save one of those manifest files to the Rendered Manifest branch. This is happening because the rendered manifests are generated with names formatted like "<manifest_name>-.yaml" which does not include the namespace. Some products like Open Cluster Management/Red Hat Advanced Cluster Management have strict requirements for the name.

Screenshots

Thi screenshot shows the input manifest files (view code in https://github.com/BenjaminNeale-Heritage/manifests-overwritten/tree/main/components/rhacm/resources/overlays/hub-cluster).

Thi screenshot shows the rendered manifest files (view code in https://github.com/BenjaminNeale-Heritage/manifests-overwritten/tree/cluster/hub-cluster/components/rhacm).

Steps to Reproduce

View config within the https://github.com/BenjaminNeale-Heritage/manifests-overwritten repository.

Version

uses: akuity/kargo-render-action@v0.1.0-rc.40

Logs

N/A

[sgarlick987]

Just ran into this as well. Our case was managing namespaces and a service account with the same name in each. To work around we've changed the service account name to be different between the namespaces. Another workaround would be to enable the combine manifests option so you just have all.yaml.