-
Notifications
You must be signed in to change notification settings - Fork 499
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
services/horizon: Add deprecation warning for using command-line flags #5051
Conversation
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.
While we're currently only adding a deprecation warning, I'm wondering if we should transition our code that uses command line parameters, both in test cases and potentially other code, to instead use environment variables before publishing the warning?
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.
Can we avoid duplicating environment.go?
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.
LGTM!
#5051) * Add deprecated warning * Add deprecated warning tests * add test for env vars * Dynamically print deprecated message * Update flags.go * Update parameters_test.go * Update parameters_test.go * Update parameters_test.go * Update parameters_test.go * Shift environment.go to horizon package * Move environment.go to test dir * Update flags_test.go * Update flags_test.go * Update integration.go * Nit changes - 1 * Update CHANGELOG.md * Nit changes - 2 * Update flags_test.go
Closes #5045
PR Checklist
PR Structure
otherwise).
services/friendbot
, orall
ordoc
if the changes are broad or impact manypackages.
Thoroughness
.md
files, etc... affected by this change). Take a look in the
docs
folder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
We recommend environment variable usage in our docs. We want to deprecate command-line flag usage and remove it completely in the future. This deprecation warning will make users move towards using env vars.
Why
Currently horizon has a ton of flags and this makes using them all very cumbersome. We want to move towards using environment variables.
Known limitations
[TODO or N/A]