Thanks to visit codestin.com
Credit goes to github.com

Skip to content

PG-1607 Fix tests and documentation around Vault TLS support #396

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 4 commits into from
Jun 6, 2025

Conversation

jeltz
Copy link
Collaborator

@jeltz jeltz commented Jun 5, 2025

This is split out from #392 since the refactoring to use TLS by default in both documentation and tests is largely unrelated to the behavioral changes I proposed there.

This makes sure we run TLS in our test suite since that is what we will use by default anyway plus also push for TLS in our documentation.

@codecov-commenter
Copy link

codecov-commenter commented Jun 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.48%. Comparing base (5c33f38) to head (94677a8).

❌ Your project status has failed because the head coverage (85.48%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@                  Coverage Diff                  @@
##           TDE_REL_17_STABLE     #396      +/-   ##
=====================================================
+ Coverage              85.40%   85.48%   +0.08%     
=====================================================
  Files                     22       22              
  Lines                   2535     2536       +1     
  Branches                 385      387       +2     
=====================================================
+ Hits                    2165     2168       +3     
+ Misses                   296      294       -2     
  Partials                  74       74              
Components Coverage Δ
access 84.20% <ø> (ø)
catalog 88.59% <ø> (ø)
common 91.80% <ø> (ø)
encryption 72.56% <ø> (ø)
keyring 72.42% <ø> (+0.47%) ⬆️
src 91.42% <ø> (+0.01%) ⬆️
smgr 97.41% <ø> (ø)
transam ∅ <ø> (∅)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@Andriciuc Andriciuc left a comment

Choose a reason for hiding this comment

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

Approved from docs side

jeltz added 4 commits June 6, 2025 14:08
…e_key_provider

Also do not rely on the Vault server setup since any file on disk will do.
This is a very basic test but before this there were no tests at all.
Since the dev mode of Vault supports generating HTTPs ceritficates we
should just use that since in production everyone will use HTTPS we
should run our tests with HTTPS too.
We should encourage HTTPS over HTTP in out examples.
@jeltz jeltz force-pushed the tde/vault-tls-cleanup branch from 6128dcf to 94677a8 Compare June 6, 2025 12:11
@jeltz jeltz merged commit 4575c03 into percona:TDE_REL_17_STABLE Jun 6, 2025
16 checks passed
@jeltz jeltz deleted the tde/vault-tls-cleanup branch June 6, 2025 15:07
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.

4 participants