I have looked over that link Dinar. I see how I can make that work, seems a bit involved for what I am trying to accomplish. I was hoping that I could setup 3 different yaml files with dev.yaml and staging.yaml and add a parameter that would point to that file and override the values.yaml file. That way I can make changes to a dev branch and have fleet deploy that to where ever fleet tells it. And then when I merge to staging I get that deployed to where ever Fleet tells it and finally when staging is merged into main/production Fleet then deploys that. Not sure where to find such a parameter to add to the Fleet manifest. I am hoping there is one.

That would also allow for using the same files and methods for installing things with helm if needed.

So one way to accomplish this is to create sub directories and symlink everything but the yaml file that couls work then you would set the branch and the path.

And I did think about that first, but was thinking others must have done this and solved it before me.

Where can I go to submit a suggestion?

Is there some documentation of the fleet.yaml file and it's options? I saw this (posted below) in an issue and if there is a way to pick values files like it looks like that would get me there.

helm:
  repo: xyz
  chart: xyz
  version: 1.9.1
  releaseName: release
  maxHistory: 3
  valuesFiles:
    - values.yml

Never mind I think i found some.

So apparently there is no way to do what I want to yet. https://github.com/rancher/fleet/issues/344