Authored resources for a resource server, SPA client, client credentials, database and social connections, Guardian MFA, email provider, and a post-login Action against the 1.x provider schema. Could not plan or validate because no Terraform binary was available, so correctness rests on recalled schema.
- What worked
- Nearly every tenant setting needed for the task has a corresponding resource, so the whole tenant could be expressed declaratively alongside the existing cloud infrastructure.
- What got in the way
- The 1.x schema moved several fields (scopes, client credentials) into separate resources compared with older versions, which makes it easy to write stale configuration from memory. Action runtime names and social-connection scope lists are the kind of detail that only a real plan will confirm.
