8000 Move section in the upgrading guide by ahus1 · Pull Request #40735 · keycloak/keycloak · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Move section in the upgrading guide #40735

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

Merged
merged 1 commit into from
Jun 27, 2025

Conversation

ahus1
Copy link
Contributor
@ahus1 ahus1 commented Jun 26, 2025

Closes #39063

This moves the section as it is IMHO not a notable change, but a deprecation. As we would eventually remove support for the old format, this is IMHO the right section.

@ahus1 ahus1 self-assigned this Jun 26, 2025
@ahus1 ahus1 marked this pull request as ready for review June 26, 2025 13:30
@ahus1 ahus1 requested a review from a team as a code owner June 26, 2025 13:30
Closes keycloak#39063

Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
@ahus1 ahus1 force-pushed the is-39063-move-deprecation branch from c69120c to d8f9e58 Compare June 26, 2025 13:30
Copy link
Contributor
@vmuzikar vmuzikar left a comment

Choose a reason for hiding this comment

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

@ahus1 Thank you for the PR.

I'm not sure I'd say this is a deprecation note. We've introduced a new format while effectively deprecating the old. So it's kinda a new feature and a deprecation. A notable change sounds more descriptive to me, though I don't have a strong opinion about it, so approving regardless.

@ahus1 ahus1 merged commit 7e2a38a into keycloak:main Jun 27, 2025
54 checks passed
@ahus1
Copy link
Contributor Author
ahus1 commented Jun 27, 2025

@vmuzikar - I hear you. AFAIK there isn't yet a warning for all SPI options in the old format, and we also don't provide a note that all SPI options (regardless if their suffix is for "enabled" or one of the other special ones). With putting this section into the "deprecated" area, it is now official that we're eventually stop supporting it.

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.

Optimized startup fails from kc.spi-connections-http-client-default-expect-continue-enabled passed at runtime
2 participants
0