Allow catalog applications to alter the git Repo on install

[abangser]

What is your feature idea?

Allow tools installed via the catalog to make additive changes to the kubefirst created git repo. In specific, generate a namespaced directory that they can control and add files to.

Why is it needed?

One of the underpinnings of Kubefirst is a belief in a GitOps workflow. This is aligned with the preferred ways of working for a lot of the installed software too. Because of this, it is not uncommon for tools to have conventions around how to read documents from a git repo and when those tools are installed via the Catalog it would be great to wire that up automatically.

More specifically, I am a contributor to kratix.io and as a part of that tool, we need to be able to write to a state store (either s3 or git protocol). In an ideal world, we would enable platform owners to colocate their Kubefirst repo and their Kratix state store. This would require a directory within the Kubefirst repo that is "owned" by Kratix.

To do this without name clashing, I would recommend that a catalog tool should be able to follow a convention to add a directory it can own in the Kubefirst repo. I was originally thinking that this could fall as a peer to the Kubefirst directory under the registry directory. But I think this can be totally up for grabs.

Is this missing feature preventing you from using kubefirst?

• [ ] Yes

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[fharper]

Thanks for the idea @abangser. As discussed on our Slack community, not sure when we'll be able to prioritize this, but I think it's a good feature idea.