Support TLS status on MySQL 8.4 - #181
Draft
Areson wants to merge 1 commit into
Draft
Conversation
Use tls_channel_status when available while retaining the legacy have_ssl fallback for older or restricted servers. Add focused and MySQL 8.0/8.4 coverage. Co-authored-by: Codex <noreply@openai.com> Ai-assisted: true
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
MySQL 8.0.26 deprecated
have_ssl, and MySQL 8.4 removed it, causing thetlscollector to fail during plan preparation.What
performance_schema.tls_channel_statuswhen available@@have_sslfor older or restricted servers and disabled Performance SchemaRisk Assessment
Low to medium — the change is limited to the TLS collector and preserves the legacy query as a compatibility fallback.
References
Closes #133
Generated with Codex