That’s right! Now you can ask the AI to deploy a module by name. Spacelift Intent resolves it against your Spacelift module registry and applies it as a single managed resource, under your existing policies, state, and audit trail. No module block, and no PR required. The guardrails already built into your registry and your Intent policies still apply.

"Deploy the elb module" resolves to the module's slug (terraform-aws-elb), picks its latest active version, and prompts for any missing inputs. Pin a version or pass inputs up front for precision: "Deploy the elb module at version 1.2.0, with the web load balancer inputs.

Before applying, Intent verifies the module is visible and active, and that every required input is set with nothing undeclared. If it fails a check then nothing will run. Pass them, and Intent evaluates your Intent policies (resource_type: spacelift/module, operation, provider: the slug, provider_version, proposed_state: your inputs), then runs the module on a worker in the background.

Updates and upgrades work the same way: "Set the idle timeout to 120" or "Upgrade to the latest version." Intent diffs the input schema between versions, and carries your existing values forward. It only asks about what's new or newly required.

Each deployment is one spacelift/module resource in your Intent project. Its managed resources are nested underneath and read-only. Every create, update, and delete action is logged in History.

Intent only deploys modules from your Spacelift module registry. It does not pull modules from the public Terraform Registry or directly from Git. The module has to be published to Spacelift first. As always, take it for a spin, and let us know what you think.

Check out the documentation here: Deploying Spacelift Modules