Expose build outside of internal for external use

[bugbuilder]

It might be useful to move build out of internal so it can be imported from outside of flux-operator, avoiding the need to build a wrapper around the Flux client. In my case, I first render and validate the objects before applying them to Flux. Currently, I need to create a client wrapper to achieve this, which is not very user-friendly.

[stefanprodan]

The Flux Operator CLI has a build instance and build reset commands for exactly this purpose. We have no plans on exposing public packages beyond the APIs. Did you tried using the CLI to generate and validate the manifests?

[bugbuilder]

In my use case, I programmatically create dynamic RSIPs and then run build rset, capture the output, and programmatically validate the resources. At the moment, I have to wrap the CLI client to achieve this.

It would be great if this build functionality were exposed as a public API, similar to how Helm exposes its functionality, so that other tools could extend or invoke it directly without relying on a CLI wrapper.