To avoid having to fiddle with SwarmCD configuration every time a new stack needs to be added, I wish to use something similar (but much simpler/simplistic) to what Argo CD provides via ApplicationSet.
My use case would be to have a single repository with multiple folders, one for each stack, and let SwarmCD detect new folders that matches a patter, for example stacks/**/docker-compose.yaml or a more regex-que stacks/.*/docker-compose.yaml.
Another approach could be a to mimic something like Argo CD "Application of Applications" pattern: be able to specify a stacks_file, instead of compose_file, inside the stacks config, to point to another stacks configuration file that would then be merged (recursively).
To avoid having to fiddle with SwarmCD configuration every time a new stack needs to be added, I wish to use something similar (but much simpler/simplistic) to what Argo CD provides via ApplicationSet.
My use case would be to have a single repository with multiple folders, one for each stack, and let SwarmCD detect new folders that matches a patter, for example
stacks/**/docker-compose.yaml
or a more regex-questacks/.*/docker-compose.yaml
.Another approach could be a to mimic something like Argo CD "Application of Applications" pattern: be able to specify a
stacks_file
, instead ofcompose_file
, inside the stacks config, to point to another stacks configuration file that would then be merged (recursively).