-
Notifications
You must be signed in to change notification settings - Fork 896
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
Deprecate symbol suport for tools/configure_server_settings #21006
Conversation
Is there a link to where this was removed? Was it deprecated first? |
#20908 - Updated the OP Also the more general ManageIQ/manageiq-api#979 I think there still needs to be a database migration for any existing symbols, which is on @kbrock 's radar, I believe. |
So, I'm guessing it would be hard to deprecate it in settings, or would it? But if so, shouldn't we deprecate the client here before we just drop support for it? |
What's to deprecate? We don't support symbols anymore and all symbols have become strings. Are you suggesting keep the symbol and spit out a deprecation, then just convert to .to_s anyway? Since it's a tool, I guess I don't really understand the purpose of deprecation? |
Yeah, but it seems odd to just drop support for |
Yeah...I have no problem deprecating, but the audience for it seems really small if at all. |
ecb54d3
to
60cd6cc
Compare
@jrafanie Updated. |
60cd6cc
to
dd253c9
Compare
Checked commit Fryguy@dd253c9 with ruby 2.6.3, rubocop 0.82.0, haml-lint 0.35.0, and yamllint |
Tests are failing with "pg_restore exit code: 1 error was: pg_restore: [archiver] could not open input file "foo/bar/mkfifo": No such file or directory"... should be fixed by #21009... kicking. |
In the move away from allowing symbols in the settings (#20908), we should drop the symbol support from this tool as well.
@jrafanie @kbrock Please review.