Skip to content

Switch to trustme for test certificates #2679

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
Nov 8, 2024
Merged

Conversation

pquentin
Copy link
Member

@pquentin pquentin commented Nov 8, 2024

Python 3.13 enforces VERIFY_X509_STRICT (RFC 5280 compliance) and the certificates generated by Elasticsearch are not compliant.

Python 3.13 enforces VERIFY_X509_STRICT (RFC 5280 compliance) and the
certificates generated by Elasticsearch are not compliant.
Copy link

github-actions bot commented Nov 8, 2024

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@pquentin pquentin merged commit a5da745 into elastic:main Nov 8, 2024
11 checks passed
@pquentin pquentin deleted the trustme branch November 10, 2024 17:54
github-actions bot pushed a commit that referenced this pull request Nov 10, 2024
github-actions bot pushed a commit that referenced this pull request Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants