-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cmd/run): --config option flag #2339
Conversation
* Introducing --config [configmap|secret|file]:name * Deprecate --configmap and --secret Ref apache#2003
The old config flag is clashing with the new one that we want to introduce for run subcommand. It makes sense to rename it as --kube-config as it makes reference to kube configuration file. Ref apache#2003
@nicolaferraro, I've added d4077a4 to this PR in order to check if a |
Introduced a new list of flags that accept multiple values. If they are passed a file: syntax, the value will be expanded with the relative file location
@nicolaferraro, I've added 5765133 which should fix the concerns related to the modeline. Indeed, that problem was wider as it was affecting the rest of flags that were using |
With this PR we are:
--config [configmap|secret|file]:name
run option flag--configmap
and--secret
run option flag--config
global flag with--kube-config
--config
The goal is to provide a unique
config
flag to manage all different kind of configuration as explained in #2003. This flag eventually differs fromresource
as it is meant to only provide configuration files that will be evaluated by theIntegration
runtime.Release Note