Thank you for sharing this. It’s really nice to see ways other people might be solving similar problems, and open sourcing something early on is really a great way of seeing the evolution of such tools.
Configuration files with gitops is always a very interesting problem whatever your underlying infra is. In my current places we’re getting them copied into gcs, importing them into databases, and even making them into config maps. Having the ability to abstract this a bit is an interesting proposition.
If you wouldn’t mind sharing a bit more on the flow you are using this in, did you have the need to push different configs to different environments? And if so, do you just ended up having different patterns and urls for each env, or is there a nicer way to do this with goose?
Configuration files with gitops is always a very interesting problem whatever your underlying infra is. In my current places we’re getting them copied into gcs, importing them into databases, and even making them into config maps. Having the ability to abstract this a bit is an interesting proposition.
If you wouldn’t mind sharing a bit more on the flow you are using this in, did you have the need to push different configs to different environments? And if so, do you just ended up having different patterns and urls for each env, or is there a nicer way to do this with goose?