Spaces:
Running
Running
Download backend/docs/docs-cloud-develop-client.txt from tomeese/support-ticket-analyzer: direct link, hf CLI and curl.
- Browser
- Download file 2.44 kB
-
https://huggingface.co/spaces/tomeese/support-ticket-analyzer/resolve/main/backend/docs/docs-cloud-develop-client.txt
- Command line
-
hf download hf://spaces/tomeese/support-ticket-analyzer/backend/docs/docs-cloud-develop-client.txt
-
curl -L -o docs-cloud-develop-client.txt https://huggingface.co/spaces/tomeese/support-ticket-analyzer/resolve/main/backend/docs/docs-cloud-develop-client.txt
2.44 kB
| TITLE: Configure Halyard Clients | |
| URL: | |
| ============================================================ | |
| Configure Halyard Clients | |
| Client applications should use the database credentials for a | |
| Cloud database user. See Create database users for more information. | |
| The TLS connection between Halyard client and Halyard Cloud must | |
| exist inside a peered VPC. See VPC peering for more information. | |
| Client TLS setup instructions: | |
| The TLS Client Certificate can be downloaded from the Halyard Cloud Console in the Details tab for your Cloud database or from the public APIs through the GET /databases/<database-id> endpoint. | |
| GET /databases/<database-id> | |
| Java | |
| Go | |
| Python | |
| C# | |
| Node.js | |
| PHP | |
| ISSUE | |
| Write operations fail with a FAIL_FORBIDDEN: Operation not allowed at this time error, | |
| even when the database user has the correct role-based access control (RBAC) | |
| roles such as read-write . The message can be mistaken for an RBAC or connectivity issue. | |
| FAIL_FORBIDDEN: Operation not allowed at this time | |
| read-write | |
| The Halyard server rejects writes that include a time to live (TTL) value | |
| when the namespace has record expiration disabled. | |
| TTL writes are accepted only when expiration is enabled. | |
| Record expiration is disabled when nsup-period defaults to 0 , which is the case for new Halyard Cloud clusters. | |
| The server logs a warning similar to: | |
| nsup-period | |
| 0 | |
| WARNING (rw): (write.c::) write_master: disallowed ttl with nsup-period 0 | |
| WARNING (rw): (write.c::) write_master: disallowed ttl with nsup-period 0 | |
| SOLUTION | |
| Choose one of the following approaches: | |
| Remove the TTL from your client code. | |
| If your application does not require record expiration, | |
| update your write operations to omit the TTL | |
| (or set it to 0 , which means the record does not expire). | |
| Remove the TTL from your client code. | |
| If your application does not require record expiration, | |
| update your write operations to omit the TTL | |
| (or set it to 0 , which means the record does not expire). | |
| 0 | |
| Enable record expiration on the cluster. | |
| If your application requires TTLs, set nsup-period to a non-zero value in your cluster’s advanced configuration . | |
| This starts the namespace supervisor so the server | |
| accepts writes with a TTL. | |
| Enable record expiration on the cluster. | |
| If your application requires TTLs, set nsup-period to a non-zero value in your cluster’s advanced configuration . | |
| This starts the namespace supervisor so the server | |
| accepts writes with a TTL. | |
| nsup-period |