Feature Request: fleet.yaml to support helmSecretName

[dbones]

Is your feature request related to a problem?

in a GitRepo, it may contain several fleet.yaml's each referencing a helm chart

example repo (the )
|- cert-manager
|  |- fleet.yaml    <- open-source no secret required
|- service-mesh
|  |- fleet.yaml    <- requires A credentials 
|- low-code
  |- fleet.yaml    <- requires B credentials

The repo in this example has 2 different secrets (A and B)

this is not supportable in the current gitRepo, there is limited support.

Solution you'd like

can we supply, the helmSecretName in the fleet.yaml, as-well (also instead) of specifying it in the gitRepo

this will allow the secret name to be specified with the context of the fleet.yaml, which specifies the helm chart

(we checked the fleet.yaml, but could not see this being a supported option)

Alternatives you've considered

multiple gitRepos configured for a git repository, per helm secret

this has a unwanted side effect, is the workloads which did not have a credential and then has a credential, would mean the bundles would be impacted, and workloads may be re-deployed when they are moved to a gitRepo which would represent the credentials.

Anything else?

No response

[kkaempf]

adding milestone to get it on our radar