Patch Configuration
Patching new configuration in all nodes can be done from bastion server. This page explains all the argument and flags available using config patch command.
The available flags are listed below:
| Flag | Duplicate | Shorthand | Usage |
|---|---|---|---|
| - -automate | - -a2 | -a | Patch configuration to all the Automate nodes. |
| - -chef_server | - -cs | -c | Patch configuration to all the Chef Server nodes. |
| - -frontend | - -fe | -f | Patch configuration to all the Frontend nodes. (Includes Automate and Chef Server) |
| - -postgresql | - -pg | -p | Patch configuration to the PostgresQL cluser. |
| - -opensearch | - -os | -o | Patch configuration to the OpenSearch cluser. |
You can use the above patches using the following format:
chef-automate config patch --< FLAG > < PATH_TO_TOML_FILE >
For Example: chef-automate config patch --frontend /home/frontend.toml
Note
- Frontend patch will be applied to all nodes where are Postgresql and OpenSearch changes will be applied to only one node of the cluser.
- After patching some services will go restart. So the health status will take upto 2 minutes to show healthy.
Warning
- For certificate rotation, don’t use
config patch. Insteadcert-rotatecommand can be used. To know more about certificate rotation click here - While patching the same from the provision host, structures such as TLS from OpenSearch configuration toml file and SSL from PostgreQL configuration toml file will be ignored.
Was this page helpful?