What problem does it solve? Provisioning Neo4j Aura cloud instances involves async lifecycle operations, one-time credential capture, OAuth2 token management, and tier/region selection that are easy to get wrong, leading to lost passwords, failed connections, and misconfigured CI/CD pipelines. ## Core Features & Use Cases - Instance Lifecycle Management: Create, pause, resume, resize, and delete AuraDB Free, Professional, Business Critical, and VDC instances using aura-cli v1.7+ or the Aura REST API. - Credential and Auth Handling: Set up OAuth2 client credentials, refresh 1-hour bearer tokens, and capture the initial password that is only shown once at creation time. - CI/CD and Terraform Provisioning: Script instance provisioning in Python or declare instances with the neo4j/neo4j-aura Terraform provider, including async status polling until running. - Use Case: A platform engineer needs an ephemeral Neo4j instance for each CI test run. The skill guides creating a Professional instance via the REST API, polling until status is running, writing credentials to .env, and tearing the instance down after tests. ## Quick Start Ask the assistant to create a Neo4j Aura Professional instance on GCP in europe-west1 using aura-cli, poll until it is running, and write the connection credentials to a .env file.
