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

KAFKA-12601: Remove deprecated delegation.token.master.key in 3.0 #10459

Conversation

ijuma
Copy link
Contributor

@ijuma ijuma commented Apr 1, 2021

This was only deprecated in 2.8, but it would be nice not to have the
racially charged term master in 3.0.

Committer Checklist (excluded from commit message)

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation (including upgrade notes)

This was only deprecated in 2.8, but it would be nice not to have the
racially charged term `master` in 3.0.
@ijuma ijuma changed the title KAFKA-12601: Remove deprecated delegation.token.master.key KAFKA-12601: Remove deprecated delegation.token.master.key in 3.0 Apr 1, 2021
@@ -1292,8 +1290,7 @@ object KafkaConfig {
.define(SaslLoginRefreshMinPeriodSecondsProp, SHORT, Defaults.SaslLoginRefreshMinPeriodSeconds, MEDIUM, SaslLoginRefreshMinPeriodSecondsDoc)
.define(SaslLoginRefreshBufferSecondsProp, SHORT, Defaults.SaslLoginRefreshBufferSeconds, MEDIUM, SaslLoginRefreshBufferSecondsDoc)
/** ********* Delegation Token Configuration ****************/
.define(DelegationTokenSecretKeyAliasProp, PASSWORD, null, MEDIUM, DelegationTokenSecretKeyAliasDoc)
.define(DelegationTokenSecretKeyProp, PASSWORD, null, MEDIUM, DelegationTokenSecretKeyDoc)
.define(DelegationTokenSecretKeyProp, PASSWORD, MEDIUM, DelegationTokenSecretKeyDoc)
Copy link
Member

Choose a reason for hiding this comment

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

It looks like some logic depends on having null as default as a bunch of tests are failing with:

org.apache.kafka.common.config.ConfigException: Missing required configuration "delegation.token.secret.key" which has no default value.

Copy link
Contributor Author

@ijuma ijuma Apr 1, 2021

Choose a reason for hiding this comment

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

Will fix if we agree that this is a good idea. :) It's more aggressive than I would usually recommend, so I'm looking for additional opinions.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mimaison so, what's your take? Should we remove this for 3.0, or keep it until 4.0?

@ijuma
Copy link
Contributor Author

ijuma commented Apr 3, 2021

Thinking about this more, since this config was previously required and the KIP-692 configs were not deprecated in time for removal in 3.0, I think we should remove this in 4.0. Closing.

@ijuma ijuma closed this Apr 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants