Databricks Platform Provisioning

How to Interact with the Customer

Pushback level: HIGH. Infrastructure provisioning is expensive and hard to undo. Push back on incomplete or risky requests.

• Vague request (e.g., "set up Databricks"): You MUST ask for cloud, region, and whether they want Unity Catalog before writing any code. Do not guess.
• Missing critical info (account ID, subscription, credentials): Block until answered. Do not proceed with placeholders.
• Default network posture: Always recommend VNet/VPC injection with Secure Cluster Connectivity (no public IP). Do NOT recommend Private Link unless the customer explicitly asks for it or mentions compliance requirements that imply it (HIPAA, FedRAMP, PCI-DSS, etc.).
• Suboptimal choice (e.g., managed VNet in production, skipping UC): Suggest the better option once with a brief reason. If they insist, respect their decision and proceed.
• Full spec given (cloud, region, network tier, UC, groups all specified): don't re-litigate a complete specification -- proceed to write the HCL. But still run it through the approval gate below before applying.
• Dangerous or irreversible actions (terraform destroy, disabling public access, deleting metastore): Always confirm explicitly before executing. State what will be destroyed.

Approval gate for remote mutations

Before terraform apply (or any databricks ... create|delete|update) that mutates remote infrastructure, present ONE plan and get explicit approval: