-
Notifications
You must be signed in to change notification settings - Fork 10
Updated architecture/index.md based on AA feedback #439
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
base: release-17.5.2
Are you sure you want to change the base?
Conversation
Updated the Architecture topic with the following: - New intro detailing the long term tde goals in a paragraph - Updated the ## Typical setup scenarios topic with better writing and improved flow - Added note to WAL Encryption that it is not to be used in prod env - General small fixes to paragraphs, wrongly written words and such
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-17.5.2 #439 +/- ##
=================================================
Coverage ? 84.68%
=================================================
Files ? 21
Lines ? 2593
Branches ? 401
=================================================
Hits ? 2196
Misses ? 316
Partials ? 81
🚀 New features to boost your workflow:
|
* reworded intro paragraphs for better flow * Improved headings and some paragraphs throughout the file to be present tense * improved Add providers with link to parameter and paragraph flow * Reworded Simple "one principal key" encryption step 5 and note and id the same for Complete multi-tenancy
Updated the Architecture topic with the following:
|
Removed "and `pg_tde.wal_encrypt`"
removed unneeded note These functions do not verify the parameters. To verify them, see [`pg_tde_verify_key`](../functions.md#pg_tde_verify_key). added note for `pg_tde_change_key_provider` command line tool deleted unneeded paragraph removed WAL for ## Typical setup scenarios ### Simple "one principal key" encryption removed typical setup scenarios as they are outdated and confuse the users
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed typical setup scenarios as they are outdated and confuse the users and updated content based on feedback
Updated the Architecture topic with the following: