automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
Automation Suite on EKS/AKS installation guide
Last updated Dec 4, 2025
When you provide an SQL connection string under the
orchestrator.testautomation section of the cluster
configuration file, the uipathctl binary ignores the connection
string and uses the one under the orchestrator section instead. As
the following sample shows, the ignored connection string is the value of the
sql_connection_str
parameter:"orchestrator": {
"testautomation": {
"enabled": true,
"sql_connection_str": "Server=tcp:new-sql-server-name,1433;Initial Catalog=new-db;Persist Security Info=False;User Id=test;Password='************';MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;Max Pool Size=100;"
}
}"orchestrator": {
"testautomation": {
"enabled": true,
"sql_connection_str": "Server=tcp:new-sql-server-name,1433;Initial Catalog=new-db;Persist Security Info=False;User Id=test;Password='************';MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=True;Connection Timeout=30;Max Pool Size=100;"
}
}To address the issue, take the following steps:
-
Perform a Base64 encoding of the SQL connection string that you provided as the value of the
sql_connection_strparameter:echo -n "<sql_connection_str under orchestrator.testautomation in cluster config file>" | base64 -decho -n "<sql_connection_str under orchestrator.testautomation in cluster config file>" | base64 -d -
Run the following command to edit the
orchestrator-secretssecret:kubectl edit secret orchestrator-secrets -n uipathkubectl edit secret orchestrator-secrets -n uipath -
In the secret, update the value of the
sqlConnectionStringTAparameter with the Base64-encoded connection string value. -
Check if you successfully updated the connection string value:
kubectl get secret orchestrator-secrets -n uipath -o jsonpath="{.data.sqlConnectionStringTA}" | base64 --decodekubectl get secret orchestrator-secrets -n uipath -o jsonpath="{.data.sqlConnectionStringTA}" | base64 --decode -
In the ArgoCD app UI, navigate to Orchestrator > Details > Parameter > Values > Inside values > Update.
-
Under the
connectionStringssection, update the value of theTestAutomationparameter with the plain-text value of the connection string, as shown in the following sample:connectionStrings: TestAutomation: <Plain-text value of sql_connection_str under orchestrator.testautomation in cluster config file>connectionStrings: TestAutomation: <Plain-text value of sql_connection_str under orchestrator.testautomation in cluster config file>
