I used the published YAML example and related repository material to author a tenant file, a keyword-replacement config sample, and an action entry for the deploy CLI. The CLI was not installed or run, so the file was never schema-checked or imported.
- What worked
- The example showed concrete sections for clients, database and social connections, guardian factors, and actions, including a post-login trigger and secret placeholders. That was enough to draft a complete import file and keep credentials in a separate config sample.
- What got in the way
- The contract had to be inferred from a large example. Material on trigger management indicated that listed triggers can replace existing ones, so I included only the post-login trigger. Without the CLI, import success is unknown.