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

Fail to start when deprecated network params are used #2913

Merged
merged 2 commits into from
Mar 14, 2024

Conversation

gerardsn
Copy link
Member

fixes #2909

Copy link
Member

@reinkrul reinkrul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we do this just for this case, or for all deprecated config we remove? Since then, we always have to spread deprecation/removal over at least 3 versions.

This only happens in non-strict mode (not posible in strict mode).

@gerardsn
Copy link
Member Author

I was thinking only for this case since it took me a couple of hours to figure out what caused this to fail. User trying to upgrade are going to be very frustrated if they have to go through the same proces.

A better option imo would be to fail (maybe just in production) if the config contains invalid parameters, but I don't know if this is possible/desirable.

Copy link
Member

@reinkrul reinkrul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can remove e.g. half a year after release of v6

@gerardsn gerardsn merged commit 9da4eaa into master Mar 14, 2024
8 of 9 checks passed
@gerardsn gerardsn deleted the iss-2909/fail-if-deprecated-network-params-are-used branch March 14, 2024 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Network: fail to start if deprecated TLS config is present
2 participants