This section outlines the process for updating BMC Helix Edge secrets and credentials that were initially set during deployment.

The following are the supported secrets:

• MQTT message bus connection details
• DB connection details
• Consul connection details
• ADE connection details
• BMC DWP connection details
• Docker registry connection details

To update the secret

1. Execute the following command to initiate the secret update process:

   Bash
   ./deploy.sh <namespace> -updatesecrets
   The script presents a list of secrets.
2. Select the index (1-6) of the secret you wish to modify. 
   The system prompts you to specify which connection details such as username, and password within the selected secret need updating.
3. For sensitive values such as passwords, select regenerate a new secret automatically.
4. If you prefer to provide a new value manually, enter it when the system prompt.
5. To skip modifying a specific field, press ENTER without entering any value.If any part of a secret is modified, the Kubernetes Helix Edge stack automatically restarts.
6. Wait for all Kubernetes services/pods to stabilize and make sure the BMC Helix Edge UI is accessible and functioning correctly.

To apply secret changes on Helix Edge nodes

If you change any secrets on the core machine, you must replicate the changes on all the BMC Helix Edge nodes.

Use the following steps on each node machine:

1. Wait until all Kubernetes pods on the Core machine are stable and the Helix Edge UI is accessible.
2. On the Core installer machine, locate the following secret files in the /tmp/ directory:
   • .mqttencpwd
   • .cnslenctok
   • nats.crt.pem
   • nats.key.pem
3. Copy these files to the /temp/ directory on each mode machine.  

4. On each node machine, navigate to the hedge-node installation and run the following commands:

   Bash
   make down
   make run env=node

5. Wait for all Docker containers to stabilize on the Node before proceeding to the next Node.

   InformationRestarting the Kubernetes-based hedge core stack might cause temporary service disruptions. Proceed with caution and plan accordingly.
   .