I have a couple of thoughts on how something like this would work. It could allow for the best of both worlds and possibly full automation. Effectively allowing resources to be represented in many TOML files in the repo and used in managed mode instead of just one big file.
One way to do it would be to allow for folder mapping based on a templating system. For instance servers might be: /servers/{name}.toml. Stacks might be /stacks/{server}/{name.toml}.
The other way I thought about doing this is allowing for the initial setup of a resource to just be the following:
- Name
- Repo
- FileName (relative to repo root)
On each resource there could be the buttons
- Refresh (would perform a pull and compare)
- Execute
- Commit
On resource sync you could scan for any new toml files that have a name, repo and filename and those could be the ones you do compares with for the larger execute and commit if you would wanted to do it at a more global level.
I have a couple of thoughts on how something like this would work. It could allow for the best of both worlds and possibly full automation. Effectively allowing resources to be represented in many TOML files in the repo and used in managed mode instead of just one big file.
One way to do it would be to allow for folder mapping based on a templating system. For instance servers might be: /servers/{name}.toml. Stacks might be /stacks/{server}/{name.toml}.
The other way I thought about doing this is allowing for the initial setup of a resource to just be the following:
On each resource there could be the buttons
On resource sync you could scan for any new toml files that have a name, repo and filename and those could be the ones you do compares with for the larger execute and commit if you would wanted to do it at a more global level.