You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When start stop is used in onpremise we are supposed to auto deploy the config but we do not build such multi cluster config
First is there a way to not specify to install the configs when start can we document on what condition we do not touch distant config
--onpremise-ssh-start-db-script string Run via ssh a custom script to start database
--onpremise-ssh-start-proxy-script string Run via ssh a custom script to start Proxy
--prov-db-start-script string Database start script
--prov-proxy-start-script string Proxy start script
The text was updated successfully, but these errors were encountered:
Today we could use a single haproxy for multiple cluster by splitting backend and frontend names via
haproxy-api-read-backend
haproxy-api-write-backend
When start stop is used in onpremise we are supposed to auto deploy the config but we do not build such multi cluster config
First is there a way to not specify to install the configs when start can we document on what condition we do not touch distant config
The text was updated successfully, but these errors were encountered: