spawning up from the cloud native Zürich Q&A, it might be interesting to offer the ability to specify a configProvider binary, which would be called by topf prior to applying config. that binary would then be responsible for gathering the various configuration patches.
some design notes:
- topf would execute the binary following the same contract/interface as the existing node/secret providers (i.e. get or something similar)
- as a convenience we might offer an option for topf to execute a multi-arg command. so that the following configProvider would also be valid:
configProvider: path/to/your/binary # could also be a script
# or
patchesDir: patches/
configProvider: "git clone github.com/your/config-repo.git -b main patches/
spawning up from the cloud native Zürich Q&A, it might be interesting to offer the ability to specify a configProvider binary, which would be called by topf prior to applying config. that binary would then be responsible for gathering the various configuration patches.
some design notes: