Environment:

Option 1: YugabyteDB-Anywhere - 2.18+

Option 2: YugabyteDB-Anywhere - All versions

Issue:

This process can be followed to manually disable YSQLSH if it is enabled.

Resolution:

IMPORTANT INFORMATION:
Once YSQL is disabled, it cannot be enabled again. Please be cautious if you intend to use YSQL workload on this universe in future.

The steps below outline the procedure needing to be followed to disable the YSQL. Reviewing the steps before executing on a system is highly recommended.

OPTION 1:

Step 1: By default, disabling YSQL from the Platform is disabled. This can be enabled by enabling the runtime config yb.configure_db_api.ysql. This runtime config is set to False by default and can be enabled. This can be enabled by setting the runtime config to True

curl -k --request PUT --url https://{hostname}/api/v1/customers/{cUUID}/runtime_config/{uUUID}/key/yb.configure_db_api.ysql --header "X-AUTH-YW-A
PI-TOKEN: {auth_token}"  --header 'Content-Type: text/plain'  --data 'true'

Step 2: Once the runtime config is set to true successfully, select the Universe "Actions" -> "Edit YSQL Configuration" and disable “Enable YSQL for this universe”. This will disable YSQL for all the database nodes for the selected universe.

OPTION 2:

Step 1: Follow this KB on How To Update Yugaware Universe Details Json to set enableYSQL = false and isYsqlServer = false  (for all the nodes) by updating Yugaware Universe Details Json. This should disable ysqlsh connectivity healthchecks for YB-Anywhere.

Step 2: Then we can edit the G-flag by going to Actions --> Edit Flags.

Step 3: Set `enable_ysql` as false on both T-server as well as Master nodes and do a rolling restart. This will disable it for the database node.