Linux, DevOps, Middleware and Cloud

Autonomous AI coding agents—such as Claude Code, Antigravity ( agy ), Aider, and custom in-house tools—have fundamentally changed software development. We have moved past simple autocomplete and static code generation into an era where LLMs have an interactive bash sub-shell with the autonomy to run commands, install packages, inspect directories, and edit files directly. Giving an autonomous process raw terminal access on your primary development workstation introduces real risks to your local environment. This post explores the operational and security risks of running agents natively, contrasts Soft Guardrails vs. Hard Isolation , and demonstrates why running agents inside Docker Sandbox ( sbx ) provides the containment needed for modern AI workflows. 1. The Reality of Running Agents on Your Host Machine When an autonomous CLI agent runs directly on macOS or Linux, it inherits the current user's security context and shell permissions: [Host Ter...

Architecture Diagram Terraform Apply ➡ Resource Group ➡ SQL Server ➡ SQL Databases ➡ Short-Term Retention (7 days) ➡ Long-Term Retention (weekly/monthly/yearly) ➡ AzAPI Update (time-based immutability) TL;DR Terraform  azurerm_mssql_database.long_term_retention_policy   cannot fully enable time-based immutability  yet. immutable_backups_enabled = true  alone  does not enforce it . Use  AzAPI ( azapi_update_resource )  to enable  timeBasedImmutability  and  timeBasedImmutabilityMode . Ensure LTR policies exist  before updating via AzAPI . Validated in portal: backups become  undeletable  until retention expires. Problem Statement Trying to enforce time-based immutability for Azure SQL database backups using Terraform: long_term_retention_policy { immutable_backups_enabled = true weekly_retention = "P1W" } ✅ T...