Short answer: You can get "SQL in a .sql file" today, without waiting for a query_file field, by defining the alerts with Python for Declarative Automation Bundles [1]. A small load_resources() function reads each .sql file and passes its contents as...
Short answer: I'd use all three, but at different layers. A per-agent rate limit is the hard backstop, a calls-per-request alert is the early warning for loops and retry storms, and cost per completed task against a 7-day baseline is a review metric,...
Short answer: the official FAQ and event pages only publish the end date (14 October 2026). They do not publish a clock time or state that the cutoff is UTC. I would treat "complete every module component on 14 October" as the requirement, finish ear...
Short answer: you can keep everything in one bundle and one databricks bundle deploy. Add a job_runs resource that runs the job that builds the tables, and reference that run from the Genie agent so the CLI creates the agent last. On a redeploy the b...
**Short answer:** keep it small. Start from the four Databricks policy families (Personal, Shared, Power User, Job Compute) and add a custom policy only where limits or cost tags really differ. Then enforce three things everywhere: a cost cap per res...
