Currently, you have to set exact prefixes in the prefix list of a FunctionConfig. Instead, it would be much simpler for the user to allow globs as well.
Specific example, instead of:
- some-repo-inprogress.my-registry.net/krm-functions
- some-repo-candidates.my-registry.net/krm-functions
- some-repo-releases.my-registry.net/krm-functions
The user could do:
- some-repo-*.my-registry.net/krm-functions
Check if it is possible to have multiple *s with some simple stdlib go package or external library. Like:
- some-repo-*.my-registry-*-cache.net/krm-functions
Currently, you have to set exact prefixes in the prefix list of a FunctionConfig. Instead, it would be much simpler for the user to allow globs as well.
Specific example, instead of:
The user could do:
- some-repo-*.my-registry.net/krm-functionsCheck if it is possible to have multiple *s with some simple stdlib go package or external library. Like:
- some-repo-*.my-registry-*-cache.net/krm-functions