From a1e4e6ba3bcd995cc65c51a8994e0fd4769b559e Mon Sep 17 00:00:00 2001 From: Ian Maddaus Date: Thu, 6 Nov 2025 10:04:30 -0500 Subject: [PATCH] Update Automate content 4.13.361 Signed-off-by: Ian Maddaus --- .../content/automate/configuration.md | 35 ++++++++++++++ .../automate/create_amazon_opensearch.md | 46 +++++++++--------- .../content/automate/create_amazon_rds.md | 48 +++++++++---------- .../ha_add_nodes_to_the_deployment.md | 1 + .../ha_aws_deployment_prerequisites.md | 16 +++---- ...ha_on_premises_deployment_prerequisites.md | 14 +++--- .../ha_remove_single_node_from_cluster.md | 2 +- .../content/automate/ha_verification_check.md | 32 ++++++++++++- .../docs-chef-io/content/automate/ldap.md | 14 ++++++ _vendor/modules.txt | 2 +- go.mod | 2 +- go.sum | 4 +- 12 files changed, 148 insertions(+), 68 deletions(-) diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/configuration.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/configuration.md index aeed02a47f..d72c8c7e1b 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/configuration.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/configuration.md @@ -505,6 +505,41 @@ and then run `chef-automate config patch ` to deploy yo x_xss_protection = "0" ``` +### Legacy Cipher Support + +Automate Dex can be configured to support legacy RSA and 3DES ciphers to connect with an LDAP/SAML server through the Dex client. + +#### Supported Ciphers + +When legacy cipher support is enabled, the following ciphers are allowed: + +- TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009C) +- TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009D) +- TLS_RSA_WITH_AES_128_CBC_SHA (0x002F) +- TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) +- TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003C) + +#### How to Enable Legacy Cipher Support + +Add the following section to your Automate configuration TOML: + +```toml +[dex.v1.sys.cipher] +enable_legacy_rsa = true +enable_legacy_3des = true +``` + +Set the following values: + +- `enable_legacy_rsa`: Enable legacy RSA key exchange ciphers. Set to true to enable. Default: false. +- `enable_legacy_3des`: Enable legacy 3DES ciphers. Set to true to enable. Default: false. + +When both are true, legacy RSA and 3DES ciphers are enabled (GODEBUG=tlsrsakex=1,tls3des=1). + +When one is true, that cipher type is enabled (GODEBUG=tlsrsakex=1 or GODEBUG=tls3des=1). + +When both are false or unset, legacy ciphers are not enabled (GODEBUG is unset). + ### Troubleshooting Common syntax errors may cause issues in configuration files: diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_opensearch.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_opensearch.md index 5c488108a2..0472539e3a 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_opensearch.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_opensearch.md @@ -24,54 +24,54 @@ Below is our guide on the steps required to create an Amazon OpenSearch cluster. Before proceeding, make sure you have the following prerequisites in place: -- An active AWS account -- Sufficient permissions to create Amazon OpenSearch clusters +1. An active AWS account +2. Sufficient permissions to create Amazon OpenSearch clusters ## Step 1: Sign in to the AWS Management Console 1. Open your preferred web browser and go to the [AWS Management Console](https://console.aws.amazon.com/). -1. Sign in to your AWS account using your credentials. +2. Sign in to your AWS account using your credentials. ## Step 2: Navigate to the Amazon OpenSearch Service Dashboard 1. Once logged in to the AWS Management Console, search for **OpenSearch** in the search bar at the top of the page. -1. Click on the **Amazon OpenSearch Service** service from the search results to open the Amazon OpenSearch Service dashboard. +2. Select the **Amazon OpenSearch Service** service from the search results to open the Amazon OpenSearch Service dashboard. ## Step 3: Create a New Amazon OpenSearch 1.3 Cluster 1. Click on **Create a new domain** button in the Amazon OpenSearch Service dashboard. -1. Enter a new **Domain name** for your OpenSearch cluster. -1. In **Domain creation method**, select **Standard create**. -1. Choose the appropriate deployment configuration, such as development or production, based on your requirements. -1. Under the **Engine options** section, select **1.3** as the version for your cluster. -1. In the **Networks** section, provide the following information: +2. Enter a new **Domain name** for your OpenSearch cluster. +3. In **Domain creation method**, select **Standard create**. +4. Choose the appropriate deployment configuration, such as development or production, based on your requirements. +5. Under the **Engine options** section, select **1.3** as the version for your cluster. +6. In the **Networks** section, provide the following information: - **VPC**: Select the VPC in which you have your automate cluster. - **Subnets**: Select all three private subnets available in your VPC. - **Security groups**: Select a security block with incoming access from your VPC CIDR range. -1. In **Fine-grained access control**, - - Enable **Fine-grained access control** - - Choose **Create master user** - - Enter the **Master username** and **Master password** you want to create -1. In **Access policy**, - - Select **Configure domain level access policy** - - Choose action **Allow**. -1. Configure the remaining settings per your requirements, such as the number of nodes and storage options. -1. Review all the settings and make sure they are accurate. -1. Click the **Confirm** button to start the cluster creation process. +7. In **Fine-grained access control**: + - Enable **Fine-grained access control**. + - Choose **Create master user**. + - Enter the **Master username** and **Master password** you want to create. +8. In **Access policy**: + - Select **Configure domain level access policy**. + - Select **Allow**. +9. Configure the remaining settings per your requirements, such as the number of nodes and storage options. +10. Review all the settings and ensure they are accurate. +11. Select **Confirm** to start the cluster creation process. ## Step 4: Wait for the Amazon OpenSearch Cluster to be Created 1. The Amazon OpenSearch cluster creation process may take several minutes. Wait for the process to complete. -1. You can monitor the progress of the cluster creation on the Amazon OpenSearch Service dashboard. +2. You can monitor the progress of the cluster creation on the Amazon OpenSearch Service dashboard. ## Step 5: Retrieve Connection Details You can obtain the necessary connection details once the Amazon OpenSearch 1.3 cluster is created successfully. 1. Go to the Amazon OpenSearch Service dashboard. -1. Find and select your newly created cluster from the list. -1. In the cluster details view, navigate to the **Endpoint** tab. -1. Here, you will find the following connection details: +2. Find and select your newly created cluster from the list. +3. In the cluster details view, select the **Endpoint** tab. +4. Here, you will find the following connection details: - **Domain name**: This is the domain name we gave for this OpenSearch cluster. - **Domain URL**: This is the endpoint or hostname of your OpenSearch cluster. It will look something like `my-opensearch-cluster-1234567890.us-east-1.es.amazonaws.com`. - **Username**: The username for accessing your OpenSearch cluster. diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_rds.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_rds.md index 4e63baf037..da92e1258b 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_rds.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/create_amazon_rds.md @@ -24,64 +24,64 @@ Below is our guide on the steps required to create an Amazon RDS PostgreSQL inst Before proceeding, make sure you have the following prerequisites in place: -- An active AWS account -- Sufficient permissions to create Amazon RDS instances +- An active AWS account. +- Sufficient permissions to create Amazon RDS instances. ## Step 1: Sign in to the AWS Management Console 1. Open your preferred web browser and go to the [AWS Management Console](https://console.aws.amazon.com/). -1. Sign in to your AWS account using your credentials. +2. Sign in to your AWS account using your credentials. ## Step 2: Navigate to the Amazon RDS Dashboard 1. Once logged in to the AWS Management Console, search for **RDS** in the search bar at the top of the page. -1. Click on the **Amazon RDS** service from the search results to open the Amazon RDS dashboard. +2. Select the **Amazon RDS** service from the search results to open the Amazon RDS dashboard. ## Step 3: Create a New Amazon RDS PostgreSQL Instance 1. Click on **Create database** button in the Amazon RDS dashboard. -1. On the **Choose a database creation method** page, select the **Standard Create** option. -1. Under the **Engine options** section, select **PostgreSQL** as the database engine. -1. Choose **PostgreSQL 13.18-R1**. -1. Under the **Templates** section, select the template that suits your needs or choose the default template. -1. In the **Settings** section, provide the following information: +2. On the **Choose a database creation method** page, select the **Standard Create** option. +3. Under the **Engine options** section, select **PostgreSQL** as the database engine. +4. Select **PostgreSQL 13.22-R2**. +5. Under the **Templates** section, select the template that suits your needs or choose the default template. +6. In the **Settings** section, provide the following information: - **DB instance identifier**: Enter a unique identifier for your RDS instance. - **Master username**: Specify the username for the master user account. - **Master password**: Set a secure password for the master user account. -1. In the **Instance configuration** section, select the appropriate instance size for your needs. -1. In the **Connectivity** section, +7. In the **Instance configuration** section, select the appropriate instance size for your needs. +8. In the **Connectivity** section: - In **Compute resource**, select **Don't connect to an EC2 compute resource**. - Select **Network type** as per your requirements. - In **Virtual private cloud**, select the VPC you want to use for your Automate cluster. - In **DB subnet group**, choose any private subnet available in your VPC. - In **Public Access** select **NO** -1. Configure the remaining settings as per your requirements. -1. Review all the settings and make sure they are accurate. -1. Click on the **Create database** button to start the creation process. +9. Configure the remaining settings as per your requirements. +10. Review all the settings and ensure they are accurate. +11. Select **Create database** to start the creation process. ## Step 4: Wait for the Amazon RDS Instance to be Created 1. The RDS instance creation process may take a few minutes. Wait for the process to complete. -1. You can monitor the progress of the instance creation on the Amazon RDS dashboard. +2. You can monitor the progress of the instance creation on the Amazon RDS dashboard. ## Step 5: Open the port in the RDS security group 1. Go to the Amazon RDS dashboard. -1. Find and select your newly created PostgreSQL instance from the list. -1. In the instance details view, navigate to the **Connectivity & security** tab. -1. Open the Security Group under **VPC security groups**. -1. Under **Inbound Rules**, edit and select **Type** as **PostgreSQL**. -1. Select **Source** as **custom** and give appropriate cidr block for your VPC. -1. Click on **Save Rules**. +2. Find and select your newly created PostgreSQL instance from the list. +3. In the instance details view, select the **Connectivity & security** tab. +4. Open the Security Group under **VPC security groups**. +5. Under **Inbound Rules**, edit and select **Type** as **PostgreSQL**. +6. Select **Source** as **custom** and give appropriate cidr block for your VPC. +7. Click on **Save Rules**. ## Step 6: Retrieve Connection Details Once the Amazon RDS PostgreSQL instance is created successfully, you can obtain the necessary connection details. 1. Go to the Amazon RDS dashboard. -1. Find and select your newly created PostgreSQL instance from the list. -1. In the instance details view, navigate to the **Connectivity & security** tab. -1. Here, you will find the following connection details: +2. Find and select your newly created PostgreSQL instance from the list. +3. In the instance details view, select the **Connectivity & security** tab. +4. Here, you will find the following connection details: - **Instance URL**: This is the endpoint or hostname of your RDS instance. It will look something like `my-rds-instance.abcdefg12345.us-east-1.rds.amazonaws.com`. - **Port**: The port number your PostgreSQL instance listens to. The default port is usually `5432`. - **Username**: The username of the master user account you specified during instance creation. diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_add_nodes_to_the_deployment.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_add_nodes_to_the_deployment.md index 1c3fcd8654..06969aa146 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_add_nodes_to_the_deployment.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_add_nodes_to_the_deployment.md @@ -99,6 +99,7 @@ Eg: `chef-automate node add --postgresql-ips 10.0.1.42 --opensearch-ips 10.0.1.4 Notice, both OpenSearch and PostgreSQL IPs are same - Similarly for frontend services (Automate and Chef Server), add both services in the same command with the same IPs Eg: `chef-automate node add --automate-ips 10.0.1.52 --chef-server-ips 10.0.1.52` +- Adding a new PostgreSQL node to the cluster may lead to increased replication lag on follower nodes because multiple nodes will concurrently attempt to sync data from the leader. {{< /note >}} Once the command executes, it will add the supplied nodes to your automate setup. The changes might take a while. diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_aws_deployment_prerequisites.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_aws_deployment_prerequisites.md index 071f88ffd8..57a3b682c5 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_aws_deployment_prerequisites.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_aws_deployment_prerequisites.md @@ -70,17 +70,17 @@ We do not support **Chef Manage** integration in the ongoing Automate version. Current Automate HA integrates with the following non-Chef tools: -**In AWS Deployment** +#### In AWS Deployment -- **SQL Database:** External not supported -- **NoSQL Database:** External not supported -- **Load Balancer:** External not supported +- **SQL Database:** External not supported +- **NoSQL Database:** External not supported +- **Load Balancer:** External not supported -**In AWS Managed Services** +#### In AWS Managed Services -- **SQL Database:** AWS RDS PostgreSQL: 13.18 -- **NoSQL Database:** AWS OpenSearch: 1.3 -- **Load Balancer:** External not supported +- **SQL Database:** AWS RDS PostgreSQL: 13.22-R2 +- **NoSQL Database:** AWS OpenSearch: 1.3 +- **Load Balancer:** External not supported ## Hardware Requirements diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_on_premises_deployment_prerequisites.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_on_premises_deployment_prerequisites.md index 1429d6560f..89603d4fb7 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_on_premises_deployment_prerequisites.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_on_premises_deployment_prerequisites.md @@ -76,10 +76,10 @@ We do not support **Chef Manage** integration in the ongoing Automate version. Current Automate HA integrates with the following non-Chef tools: -- **SQL Database:** PostgreSQL: 13.18 -- **NoSQL Database:** OpenSearch: 1.3.7 -- **Load Balancer:** - - [Kemp LoadMaster](https://kemptechnologies.com/?_gl=1*jfw3dz*_gcl_au*MTIzMDA0NzAwNC4xNzM4NjA3NTQ3*_ga*MTk4NzcyMzc0My4xNzM4NjA3NTQ3*_ga_9JSNBCSF54*MTc0NDYxNTI1MS4xNC4xLjE3NDQ2MzQ4NTcuMzUuMC4w) (Preferred) +- **SQL Database:** PostgreSQL: 13.22 +- **NoSQL Database:** OpenSearch: 1.3.20 +- **Load Balancer:** + - [Progress Kemp LoadMaster](https://kemptechnologies.com/?_gl=1*jfw3dz*_gcl_au*MTIzMDA0NzAwNC4xNzM4NjA3NTQ3*_ga*MTk4NzcyMzc0My4xNzM4NjA3NTQ3*_ga_9JSNBCSF54*MTc0NDYxNTI1MS4xNC4xLjE3NDQ2MzQ4NTcuMzUuMC4w) (Preferred) - NGINX: 1.21.3 - HA Proxy: 2.2.18 - AWS Application Load Balancer @@ -216,15 +216,15 @@ Set up the databases with password-based authentication. ### AWS Managed -- AWS RDS PostgreSQL: 13.14 +- AWS RDS PostgreSQL: 13.22-R2 - AWS OpenSearch: 1.3 Configure the backup only with **S3** when using AWS managed databases. ### Customer Managed -- PostgreSQL: 13.14 -- OpenSearch: 1.3.7 +- PostgreSQL: 13.22 +- OpenSearch: 1.3.20 ## Upgrade diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_remove_single_node_from_cluster.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_remove_single_node_from_cluster.md index b3d85a3a6a..28afe9e7ff 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_remove_single_node_from_cluster.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_remove_single_node_from_cluster.md @@ -19,7 +19,7 @@ Chef Automate HA comes with five different types of deployment flows. This page {{< warning >}} -- We do not recommend removing any node from the backend cluster, but replacing it is recommended. To learn more, see the [replace node in automate ha cluster](#replace-node-in-automate-ha-cluster) section. +- We do not recommend removing any node from the backend cluster, but replacing it is recommended. To replace a backend node, first [add a node to the cluster](/automate/ha_add_nodes_to_the_deployment/) and then [remove the relevant node from the cluster](/automate/ha_remove_single_node_from_cluster/). - Removal of nodes for PostgreSQL or OpenSearch is at your own risk and may result in data loss. Consult your database administrator before trying to delete PostgreSQL or OpenSearch nodes. - Below process can be done for `chef-server` and `automate`. diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_verification_check.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_verification_check.md index de2904b0d2..b07b15fe7d 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_verification_check.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ha_verification_check.md @@ -33,6 +33,12 @@ chef-automate verify --config config.toml The above command will trigger the `config.toml` file with config, the one you want to deploy. +To view detailed debug logs in the console, you can use the debug flag: + +```bash +chef-automate verify --config config.toml -d +``` + The post deployment CLI command is as follows: ```bash @@ -75,4 +81,28 @@ An example of a checks performed are shown in the below image: The above image shows the checks performed for Automate node. The checks in the above image are also performed on all the nodes in Automate HA, i.e., Chef Server, PostgreSQL, OpenSearch, and Chef Automate (the one showed above). -THe verify command checks all the nodes in Automate HA and with that it also provides the remediation steps for failures. +The verify command checks all the nodes in Automate HA and it also provides the remediation steps for failures. + +## Additional Verification in System Logs + +In addition to running the chef-automate verify command, you can inspect system logs for deeper insights into the verification service. + +### On the Bastion Host + +To view logs related to the automate-verify service on the bastion host, use: + +```bash +journalctl -u automate-verify +``` + +This helps identify which API checks may have failed during verification. + +### On Individual Nodes + +Based on the failed API identified from the bastion logs, you can run the same command on the corresponding node to validate the service response: + +```bash +journalctl -u automate-verify +``` + +This provides node-level visibility into the verification process and helps when troubleshooting specific failures. diff --git a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ldap.md b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ldap.md index ab04027a3e..ed62e7d54b 100644 --- a/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ldap.md +++ b/_vendor/github.com/chef/automate/components/docs-chef-io/content/automate/ldap.md @@ -956,6 +956,20 @@ With an additional `group_query_filter`, the final filter is Note: if the user entry contains more than one `filter_groups_by_user_attr` attribute, multiple queries will be executed, and their results combined. +#### TLS Handshake Failure After Upgrade + +If you encounter errors like the following one after upgrading Chef Automate, and you can still authenticate using `ldapsearch` but not through Automate, your LDAP server may require legacy RSA or 3DES ciphers for TLS connections: + +``` +automate-dex.default(O): time="..." level=error msg="Failed to login user: failed to connect: LDAP Result Code 200 \"Network Error\": remote error: tls: handshake failure" +``` + +**Solution:** + +Enable legacy cipher support in Automate Dex by following the instructions in the [Chef Automate Configuration Documentation: Legacy Cipher Support](https://docs.chef.io/automate/configuration/#legacy-cipher-support). + +This allows Automate Dex to connect to older LDAP servers using the required ciphers. See the configuration documentation for supported ciphers and step-by-step instructions. + #### Other Common Issues If a user, following a sign in through LDAP or SAML, sees a diff --git a/_vendor/modules.txt b/_vendor/modules.txt index 7e7811e609..efea8a32fd 100644 --- a/_vendor/modules.txt +++ b/_vendor/modules.txt @@ -1,4 +1,4 @@ -# github.com/chef/automate/components/docs-chef-io v0.0.0-20250902130712-4abbca2f9c80 +# github.com/chef/automate/components/docs-chef-io v0.0.0-20251106140316-cca3ad103bd3 # github.com/chef/desktop-config/docs-chef-io v0.0.0-20240814044820-5af667d41a43 # github.com/habitat-sh/habitat/components/docs-chef-io v0.0.0-20250905124722-c1a4eb639cba # github.com/habitat-sh/on-prem-builder/docs-chef-io v0.0.0-20250805192817-f8b1dae05d5e diff --git a/go.mod b/go.mod index 39f2030a81..78f279aec4 100644 --- a/go.mod +++ b/go.mod @@ -3,7 +3,7 @@ module github.com/chef/chef-web-docs go 1.23 require ( - github.com/chef/automate/components/docs-chef-io v0.0.0-20250902130712-4abbca2f9c80 // indirect + github.com/chef/automate/components/docs-chef-io v0.0.0-20251106140316-cca3ad103bd3 // indirect github.com/chef/chef-docs-theme v0.0.0-20251013213507-f2f920c69eed // indirect github.com/chef/chef-server/docs-chef-io v0.0.0-20251103154204-52161ef2177d // indirect github.com/chef/chef-workstation/docs-chef-io v0.0.0-20250930142111-8c07fe8a2202 // indirect diff --git a/go.sum b/go.sum index 472c9db43a..72929b2a12 100644 --- a/go.sum +++ b/go.sum @@ -1,5 +1,5 @@ -github.com/chef/automate/components/docs-chef-io v0.0.0-20250902130712-4abbca2f9c80 h1:JQEuqGaOg0DgvwbMwbMSzEiqcxPa14flEo9TKmPDSnU= -github.com/chef/automate/components/docs-chef-io v0.0.0-20250902130712-4abbca2f9c80/go.mod h1:juvLC7Rt33YOCgJ5nnfl4rWZRAbSwqjTbWmcAoA0LtU= +github.com/chef/automate/components/docs-chef-io v0.0.0-20251106140316-cca3ad103bd3 h1:fWEZNLetphz255JfZ5C+ivbixQ51MAqSTr7v+4pu1z0= +github.com/chef/automate/components/docs-chef-io v0.0.0-20251106140316-cca3ad103bd3/go.mod h1:juvLC7Rt33YOCgJ5nnfl4rWZRAbSwqjTbWmcAoA0LtU= github.com/chef/chef-docs-theme v0.0.0-20251013213507-f2f920c69eed h1:zzYwORxTQRu+9wzABpfRqKubuEHrLbhgbPN6Sy72tMs= github.com/chef/chef-docs-theme v0.0.0-20251013213507-f2f920c69eed/go.mod h1:+Jpnv+LXE6dXu2xDcMzMc0RxRGuCPAoFxq5tJ/X6QpQ= github.com/chef/chef-server/docs-chef-io v0.0.0-20251103154204-52161ef2177d h1:lX/Rkq2K/937kMO1XB6HcTTm+1D34s78dB3tYhY5WqM=