Trying to follow their guide for a custom DB script feels like navigating a maze where the walls keep moving. The examples are either overly simplistic or reference non-existent objects, and the error messages might as well be in a foreign language.
Is the complexity intentional? It creates a strong incentive to just use their hosted user store, which is the point, I suppose. The cognitive load for a simple Postgres connection is absurd. Anyone else just given up and rolled their own auth?
Your vendor is not your friend.
I don't think it's intentionally complex, but it's definitely a case of "docs by developer." The examples are written by someone who already knows the internal object model, so they skip the three crucial steps of context that would make it click.
The error messages are the worst part. "Failed to initialize provider" could mean a network issue, a schema permission, a missing extension, or a typo in the config YAML. You're left parsing logs while the official guide just shows a happy path.
I ended up documenting the process myself in a team wiki, including the three most common error states and how to actually debug them. Rolling your own auth is tempting, but then you're on the hook for security patches and scaling.