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

Allow commandline overrides 3.4 #12269

Closed

Conversation

dbavatar
Copy link
Contributor

@dbavatar dbavatar commented Sep 3, 2020

Cherry-pick of #12268 from master

Addressing issue #12222 see #12222 (comment)

It is a valid workflow to to have defaults in your environmental variables, and then override them on-demand with commandline parameters. The existing change unnecessarily breaks existing clusters when upgrading to 3.4+. I will also do a PR for release-3.4 cherry-pick.

@dbavatar dbavatar marked this pull request as draft September 3, 2020 20:58
This reverts commit 748ab8c.

This is an unnecessary breaking change from upgrading from 3.3, also
having both environmental variables and being able to override them
via commandline is a highly desired feature.
It should not be a warning: the user explicitly requested an override.
@dbavatar dbavatar force-pushed the allow-commandline-overrides-3.4 branch from 3612ee2 to cb907dc Compare September 3, 2020 21:02
@stale
Copy link

stale bot commented Dec 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 2, 2020
@stale stale bot closed this Dec 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

1 participant