Skip to content
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

Remove deprecated CLI flags #2738

Closed
7 tasks done
yurishkuro opened this issue Jan 22, 2021 · 6 comments
Closed
7 tasks done

Remove deprecated CLI flags #2738

yurishkuro opened this issue Jan 22, 2021 · 6 comments
Labels
good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement

Comments

@yurishkuro
Copy link
Member

yurishkuro commented Jan 22, 2021

We've accumulated a lot of deprecated flags, it would be good to remove them. Need to verify some of these, but I think all of them are past their expiration date.

We should not clean them in a single PR since they usually require code changes, better to do one PR per flag.

$ grep -rin '(deprecated' .
./cmd/flags/admin.go:39:	healthCheckHTTPPortWarning = "(deprecated, will be removed after 2020-03-15 or in release v1.19.0, whichever is later)"
./cmd/flags/admin.go:40:	adminHTTPPortWarning       = "(deprecated, will be removed after 2020-06-30 or in release v1.20.0, whichever is later)"
./cmd/collector/app/builder_flags.go:45:	collectorHTTPPortWarning       = "(deprecated, will be removed after 2020-06-30 or in release v1.20.0, whichever is later)"
./cmd/collector/app/builder_flags.go:46:	collectorGRPCPortWarning       = "(deprecated, will be removed after 2020-06-30 or in release v1.20.0, whichever is later)"
./cmd/collector/app/builder_flags.go:47:	collectorZipkinHTTPPortWarning = "(deprecated, will be removed after 2020-06-30 or in release v1.20.0, whichever is later)"
./cmd/agent/app/reporter/flags.go:51:		flags.String(AgentTagsDeprecated, "", "(deprecated) see --"+agentTags)
./cmd/query/app/flags.go:42:	queryPortWarning        = "(deprecated, will be removed after 2020-08-31 or in release v1.20.0, whichever is later)"
./cmd/query/app/flags.go:43:	queryHOSTPortWarning    = "(deprecated, will be removed after 2020-12-31 or in release v1.21.0, whichever is later)"
./plugin/storage/cassandra/options.go:237:		"(deprecated) Jaeger will automatically detect the version of the dependencies table")
./plugin/storage/cassandra/options.go:241:		"(deprecated) Enable (or disable) host key verification. Use "+nsConfig.namespace+".tls.skip-host-verify instead")
./plugin/storage/es/options.go:186:		"(deprecated, will be removed in release v1.21.0. Please use "+nsConfig.namespace+".max-doc-count). "+
./pkg/config/tlscfg/flags.go:54:		flags.Bool(c.Prefix+tlsEnabledOld, false, "(deprecated) see --"+c.Prefix+tlsEnabled)
./pkg/config/tlscfg/flags.go:69:		flags.Bool(c.Prefix+tlsEnabledOld, false, "(deprecated) see --"+c.Prefix+tlsEnabled)
./pkg/config/tlscfg/flags.go:74:	flags.String(c.Prefix+tlsClientCAOld, "", "(deprecated) see --"+c.Prefix+tlsClientCA)
@yurishkuro yurishkuro added good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement labels Jan 22, 2021
@pradeepnnv
Copy link
Contributor

I'd like to submit a PR for removing healthCheckHTTPPortWarning.

@BernardTolosajr
Copy link
Contributor

BernardTolosajr commented Jan 30, 2021

I'd like to work on removing adminHTTPPortWarning. Thanks

@LostLaser
Copy link
Contributor

LostLaser commented Jan 31, 2021

I can pick up collectorHTTPPortWarning, collectorGRPCPortWarning, and collectorZipkinHTTPPortWarning

@yurishkuro yurishkuro mentioned this issue Jan 31, 2021
5 tasks
pradeepnnv added a commit to pradeepnnv/jaeger that referenced this issue Jan 31, 2021
Fixes jaegertracing#2738

Signed-off-by: pradeepnnv <pradeepnnv@gmail.com>
pradeepnnv added a commit to pradeepnnv/jaeger that referenced this issue Jan 31, 2021
Add breaking change entry to CHANGELOG

Fixes part of jaegertracing#2738

Signed-off-by: pradeepnnv <pradeepnnv@gmail.com>
pradeepnnv added a commit to pradeepnnv/jaeger that referenced this issue Feb 1, 2021
Update Change log to use actual CLI Flags instead of variable names.

Fixes part of jaegertracing#2738

Signed-off-by: pradeepnnv <pradeepnnv@gmail.com>

Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
pradeepnnv added a commit to pradeepnnv/jaeger that referenced this issue Feb 1, 2021
Update Change log to use actual CLI Flags instead of variable names.

Fixes part of jaegertracing#2738

Signed-off-by: pradeepnnv <pradeepnnv@gmail.com>

Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Signed-off-by: pradeepnnv <pradeepnnv@gmail.com>
@yurishkuro yurishkuro reopened this Feb 1, 2021
@yurishkuro
Copy link
Member Author

@rjs211 I just noticed that you had to juggle various permutations of the old settings, but according to the deprecation timestamp, both -query.port and -query.host-port are due to be removed. Since we're doing this clean-up for the next release anyway, would you like to remove them as part of this ticket, and possibly simplify the logic (as well as the CHANGELOG)?

@rjs211
Copy link
Contributor

rjs211 commented Feb 2, 2021

@yurishkuro Sure. Will do this first. I'll move to #2249 after this.

@yurishkuro
Copy link
Member Author

Thanks everyone, this was a fun collective effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement
Projects
None yet
Development

No branches or pull requests

5 participants