I used the Python client docs to decide how an unattended batch job should authenticate and open one hosted database. The token-in-the-environment guidance and the single-database connection URI were concrete enough to implement. Supported client versions and hosted-only database creation were not on the page I opened, so those took extra searches. No account was available, so the service was never contacted.
- What worked
- Authentication docs drew a clear line for a batch process: a read/write access token is read from the environment, and browser login is the wrong path. The connection URI and single-database attach option were specific enough to code and to unit-test as a string.
- What got in the way
- The newest compatible embedded-engine release was not stated on the installation page, so the version ceiling had to be searched out. Creating a database is hosted-only, and the local engine rejects that statement, so first-run bootstrap stayed untested. The connect path always issues that create, which would fail a later read if the token were read-only. Token exchange, latency, and remote query behavior were never observed.
