-
Notifications
You must be signed in to change notification settings - Fork 381
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
cmd: Remove deprecated --config-file flag #1498
cmd: Remove deprecated --config-file flag #1498
Conversation
The podinfo integration tests failed on three attempts with "Condition never satisfied":
but locally they pass, and this PR shouldn't affect them. I'll retry once again, maybe we need to increase the timeout. UPDATE: ok, I just had to rebase with main and it's all green now. |
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
68a204a
to
4d1d16c
Compare
Signed-off-by: Anna Kapuscinska <anna@isovalent.com>
4d1d16c
to
239f57a
Compare
I'm sort of attached to that flag but ok away it goes. |
log.Warnf("Flag --%s has been deprecated, please use --%s instead", keyConfigFile, keyTracingPolicy) | ||
option.Config.TracingPolicy = viper.GetString(keyConfigFile) | ||
} | ||
// if both --config-file and --tracing-policy are set, the latter takes priority | ||
if viper.IsSet(keyTracingPolicy) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could have removed this (now useless) check
According to the code comments the
--config-file
flag should have been removed in the v0.11 release, but it hasn't been. Let's remove it before the next release.Ref #651