Skip to content
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

PG-1457 Rename principal key on user API level to just a key #154

Open
wants to merge 9 commits into
base: PG-1457-key-management-funcs-renaming
Choose a base branch
from

Conversation

artemgavrilov
Copy link
Collaborator

@artemgavrilov artemgavrilov commented Mar 19, 2025

PG-1457

This PR replaces principal key with just a key on user API level, as it's the only key that user can directly interact with.

This PR is made on top of #126

@@ -201,12 +201,12 @@ Use these functions to create a new principal key for a specific scope such as a

Princial keys are stored on key providers by the name specified in this function - for example, when using the Vault provider, after creating a key named "foo", a key named "foo" will be visible on the Vault server at the specified mount point.

### pg_tde_set_principal_key
###
Copy link
Collaborator

Choose a reason for hiding this comment

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

You accidentally deleted this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yep

BTW this PR is made on top of #126
So it contains a lot of commits from there, please review 126 first

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

@artemgavrilov artemgavrilov changed the base branch from release-17.4 to PG-1457-key-management-funcs-renaming March 20, 2025 10:13
@artemgavrilov artemgavrilov marked this pull request as ready for review March 20, 2025 13:30
@artemgavrilov artemgavrilov requested a review from jeltz March 20, 2025 13:30
@@ -201,12 +201,12 @@ Use these functions to create a new principal key for a specific scope such as a

Princial keys are stored on key providers by the name specified in this function - for example, when using the Vault provider, after creating a key named "foo", a key named "foo" will be visible on the Vault server at the specified mount point.

### pg_tde_set_principal_key_using_database_key_provider
### pg_tde_set_key_using_database_key_provider

Creates or rotates the principal key for the current database using the specified database key provider and key name.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we keep the notion of a principal key?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Probably yes. They still principal by meaning, but they are only available to the user.

What do you think @dutow ?

Copy link
Collaborator

Choose a reason for hiding this comment

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

yes, it is still called principal key, we just simplified the names of the functions.

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