Merge pull request #358 from percona/PS-9325

PS-9325 Remove info about Keyring file plugin from PS 8.4 (8.4)

Author: patrickbirch

docs/encrypt-logs.md

@@ -12,7 +12,7 @@ Changing the encryption does not change existing redo log pages. Setting the opt
 
 The metadata for the redo log encryption includes the tablespace encryption key and is stored the in redo log file header. Removing the encryption metadata disables the redo log encryption.
 
-Without the keyring plugin or component or the encryption key, a normal restart is not possible. InnoDB scans the redo log pages during startup. If the encryption options are not available, InnoDB cannot scan these pages. A forced startup without the redo logs is possible.
+Without the keyring component or the encryption key, a normal restart is not possible. InnoDB scans the redo log pages during startup. If the encryption options are not available, InnoDB cannot scan these pages. A forced startup without the redo logs is possible.
 
 ## Option
 
@@ -44,7 +44,7 @@ Changing the encryption does not change existing undo log pages. Setting the opt
 
 The metadata for the redo log encryption includes the tablespace encryption key and is stored the in undo log file header.
 
-The server requires the keyring plugin or keyring component used to encrypt log data until that data is truncated, even if the current option setting is `OFF`. When the undo tablespace is truncated, the encryption header is removed.
+The server requires the keyring component used to encrypt log data until that data is truncated, even if the current option setting is `OFF`. When the undo tablespace is truncated, the encryption header is removed.
 
 
 ## `innodb_undo_log_encrypt`

docs/keyring-components-plugins-overview.md

@@ -1,14 +1,14 @@
-# Keyring components and plugins overview
+# Keyring components overview
 
-Percona Server supports a keyring that enables internal server components and plugins to store sensitive information securely for later retrieval.
+Percona Server supports a keyring that enables internal server components to store sensitive information securely for later retrieval.
 
 !!! warning
 
-    Enable only one keyring plugin or one keyring component at a time for each server instance. Enabling multiple keyring plugins or keyring components or mixing keyring plugins or keyring components is not supported and may result in data loss.
+    Enable only one keyring component at a time for each server instance. Enabling multiple keyring components is not supported and may result in data loss.
 
-Percona Server supports the following keyring components and plugins:
+Percona Server supports the following keyring components:
 
-[Use the keyring file component or plugin :material-arrow-right:](use-keyring-file.md){.md-button}
+[Use the keyring file component :material-arrow-right:](use-keyring-file.md){.md-button}
 
 [Use the keyring vault component :material-arrow-right:](use-keyring-vault-component.md){.md-button}
 

docs/use-keyring-file.md

@@ -1,32 +1,10 @@
-# Use the keyring file component or keyring file plugin
+# Use the keyring file component
 
-## Use the keyring file plugin
-
-Percona Server for MySQL supports the keyring_file plugin that stores the keyring data locally.
-
-!!! warning
-
-    The `keyring_file` plugin should not be used for regulatory compliance.
-
-To install the plugin, follow the [installing and uninstalling plugins] instructions.
-
-### Load the keyring plugin
-
-You should load the plugin at server startup with the `--early-plugin-load` option to enable keyrings.
-
-We recommend that you load the plugin in the configuration file to facilitate recovery for encrypted tables. Also, the redo log encryption and the undo log encryption cannot be used without `--early-plugin-load`. The normal plugin load happens too late at startup.
-
-To load the keyring_file plugin, run the following command:
-
-```{.bash data-prompt="$"}
-$ mysqld --early-plugin-load="keyring_file=keyring_file.so"
-```
-
-If a server starts with different plugins loaded early, the `--early-plugin-load` option should contain the plugin names in a double-quoted list with each plugin name separated by a semicolon. The use of double quotes ensures the semicolons do not create issues when the list is executed in a script.
+The `keyring_file` component is part of the component-based MySQL infrastructure which extends the server capabilities.
 
-## Use the keyring file component
+!!! important
 
-The `keyring_file` component is part of the component-based MySQL infrastructure which extends the server capabilities.
+    Percona Server for MySQL {{vers}} does not support the `keyring_file` plugin.
 
 See the MySQL documentation on the [component installation] and on the [keyring_file component usage] for more information.
 
@@ -51,5 +29,4 @@ An example of `/lib/plugin/component_keyring_file.cnf`:
 ```
 
 [component installation]: https://dev.mysql.com/doc/refman/{{vers}}/en/keyring-component-installation.html
-[keyring_file component usage]: https://dev.mysql.com/doc/refman/{{vers}}/en/keyring-file-component.html
-[installing and uninstalling plugins]: https://dev.mysql.com/doc/refman/{{vers}}/en/plugin-loading.html
+[keyring_file component usage]: https://dev.mysql.com/doc/refman/{{vers}}/en/keyring-file-component.html

mkdocs-base.yml

@@ -265,14 +265,6 @@ nav:
         - isolation-levels.md
         - transaction-mgmt.md
         - views.md
-
-
-
-
- 
-
-
-
     - extended-show-grants.md
     - restrict-dynamic-log-locations.md
     - clone-plugin.md
@@ -299,7 +291,7 @@ nav:
     - encryption-functions.md
     - Data-at-rest-encryption:
       - data-at-rest-encryption.md
-      - Keyring components and plugins:
+      - Keyring components:
         - keyring-components-plugins-overview.md
         - use-keyring-file.md
         - use-keyring-vault-component.md