feat: add renderer pipeline support to manifest generation in

[JohnBlackwell]

Test Plan

Test environment: https://console.plrl-dev-aws.onplural.sh/

Checklist

• I have added a meaningful title and summary to convey the impact of this PR to a user.
• I have deployed the agent to a test environment and verified that it works as expected.
  • Agent started successfully.
  • Logs are clean and do not contain errors.
  • Component trees are working as expected.
• I have added tests to cover my changes.
• If required, I have updated the Plural documentation accordingly.

[linear]

PROD-3699 add renderer pipeline support to manifest generation in deployment operator

[github-advanced-security]

Trivy found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[michaeljguarino]

You need to make sure the pr checks pass (its our way of ensuring the code has been tested e2e before merge)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	github.com/​pluralsh/​console/​go/​client@​v1.58.1 ⏵ v1.58.2	+1

View full report

[michaeljguarino]

this is generally fine, but I think we need to ensure two things:

1. The default renderer should still run. This helps with the primary usecase here of supporting a helm chart and some additional git sourced manifests in one shot
2. allManifests needs to be deduped at the end (very possible you could have two renderers generate the same thing). My guess is there's dedupe elsewhere done the chain that can be imitated, otherwise it's just lo.UniqBy(...) with a key using gvk namespace + name of the unstructured resource

[JohnBlackwell]

Can you clarify your first point? My understanding was that the default renderer would run 1) if no renderers were defined or 2) if >1 renderer is defined and one of them is AUTO with AUTO meaning to use the default renderer.

Are you saying that the default renderer should run every time regardless of what renderers are defined?

[JohnBlackwell]

Also, in the case of a dup, which renderer version should be kept? ie. if both raw and helm are rendered and a dup is detected, do we want the raw or do we want the helm?

[michaeljguarino]

1. No we should run it regardless, or at least if it's just a helm chart. The most common usecase here is i want to install a chart + a few crs, and that's the nicest solve to handle that.

2. For dupes, just keep the last one in the chain, we can write some conditions on it, but for now that's fine.