22 posts tagged with "iac"

Tutorial 3 introduced stackql-deploy against a single Google Cloud project. One manifest, one provider, one VPC. The framework proved its shape: declarative resources described as SQL-anchored files, an exists-create-statecheck-exports loop that runs idempotently against live cloud APIs, no state file to maintain.

This tutorial takes the same framework and puts it to work across two clouds at once. One manifest declares both a GCP VPC and an AWS VPC. One build command provisions both in the same run. The manifest becomes a single source of truth for infrastructure that spans providers, without introducing a second tool or a second DSL.

Along the way, the AWS side of the walkthrough shows features that the minimal Google example does not need: per-environment values, tag-based resource identification, resource composability through exports, and provider-specific query helpers. The interesting part is not just deploying to two clouds, but managing both through the same manifest and lifecycle.

Tutorial 2 in this series showed the query-before-mutation pattern by hand. Query live state, apply a policy gate, mutate what's out of policy, verify convergence. Every step was a SQL statement typed into a shell. The pattern held, but the shape was low-level. One resource at a time. One session at a time. No structure for repeating it across environments or holding it right over time.

stackql-deploy takes that pattern and turns it into a framework. Define your resources once as SQL-anchored files, declare them in a manifest, and let the framework run the exists check, the create-or-update, the state check, and the exports as a single build. Same underlying pattern, now something a team can operate at scale.

This tutorial walks through the tool end to end. What it is, how a project is shaped, how a single resource is defined, and how the whole thing runs against a real Google Cloud project.

Latest release or the datadog provider for StackQL is now available, enabling SQL-based querying and management of Datadog cloud resources. The new datadog provider includes:

• coverage for the latest Datadog features
• simplified service organization
• enhanced user documentation

For more see the Datadog Provider User Docs.

⭐ us on GitHub and join our community!

Latest release or the Linode provider for StackQL is available, enabling SQL-based querying and management of Linode cloud resources.

Provider Overview​

The Linode provider offers comprehensive access to 20 services covering the entire Linode platform, with 136 resources and 425 methods, allowing you to extract data and insights from your Linode environment using familiar SQL syntax.

Key Services​

The provider includes access to:

• Compute: Manage Linode instances and configurations
• Storage: Control volumes and object storage
• Networking: Handle IPs, VLANs, VPCs, and firewall rules
• Kubernetes: Administer LKE clusters and node pools
• Databases: Manage Linode's database service
• Account & Billing: Access account information and billing details

Example Queries​

Get Account Information​

SELECT 
  company,
  country,
  balance,
  balance_uninvoiced,
  active_since
FROM linode.account.account;

List Database Engines​

SELECT
  id,
  engine,
  version
FROM linode.databases.engines;

View Regional Availability​

SELECT
  available,
  plan,
  region
FROM linode.regions.availability;

List Linode Instances​

SELECT
  id,
  label,
  region,
  status,
  type,
  ipv4,
  tags
FROM linode.linode.instances;

Getting Started​

To use the Linode provider, simply register it and set your authentication:

-- Pull the provider
registry pull linode;

-- Set your authentication
SET linode.global.auth.credentialsenvvar = 'LINODE_TOKEN';

⭐ us on GitHub and join our community!

The new deno provider for StackQL is now available, enabling developers to query and manage Deno Deploy resources using familiar SQL syntax. This provider allows you to interact with Deno Deploy's control plane API, giving you complete control over your organizations, projects, deployments, domains, and KV databases through a consistent SQL interface.

The Deno Deploy provider offers comprehensive coverage of the Deno Deploy API, organized into logical services that mirror Deno's resource structure:

With the deno provider for StackQL, you can now include Deno Deploy in your infrastructure-as-code workflows, analytics dashboards, and cross-cloud orchestration processes using the same SQL syntax you use for other cloud providers.

For more information on the Deno Deploy provider for StackQL, see the Deno Deploy Provider Docs which provides detailed documentation for every resource and method, along with ready-to-use SQL examples.

Getting Started​

To start using the deno provider, simply pull it from the StackQL registry:

registry pull deno;

You'll need to set up your authentication by exporting your Deno API token:

export DENO_DEPLOY_TOKEN="your_deno_api_token"

Then you can begin querying your Deno Deploy resources:

-- List all projects in an organization
SELECT 
  id,
  name,
  description,
  createdAt,
  updatedAt
FROM deno.project.projects
WHERE organizationId = 'your-org-id';

|-----------------------------|-------------|--------------------------------------|----------------------|-----------------------------|
|          createdAt          | description |                  id                  |         name         |          updatedAt          |
|-----------------------------|-------------|--------------------------------------|----------------------|-----------------------------|
| 2022-12-13T04:20:13.379555Z |             | 34f9440f-3275-40e2-b327-2ea65269feb5 | stackql-dev-registry | 2025-09-06T00:47:04.579279Z |
|-----------------------------|-------------|--------------------------------------|----------------------|-----------------------------|
| 2022-12-13T04:16:22.054548Z |             | 616de983-3e37-4f44-a99f-b6bb5c59e80a | stackql-registry     | 2025-09-06T01:22:46.872203Z |
|-----------------------------|-------------|--------------------------------------|----------------------|-----------------------------|

-- List deployments with key information
SELECT
  id,
  description,
  status,
  JSON_EXTRACT(domains, '$[0]') as domain,
  JSON_EXTRACT("databases", '$.default') as db_id,
  createdAt,
  updatedAt
FROM deno.deployment.deployments
WHERE projectId = 'your-project-id'
AND "order" = 'desc';

|--------------|--------------------------------|---------|----------------------------------------|--------------------------------------|-----------------------------|-----------------------------|
|      id      |          description           | status  |                 domain                 |                db_id                 |          createdAt          |          updatedAt          |
|--------------|--------------------------------|---------|----------------------------------------|--------------------------------------|-----------------------------|-----------------------------|
| pe60nqshxq3g | Latest deployment              | success | example.com                            | 8971aec3-f72f-44c4-bc9f-0b2a513bd9fc | 2025-09-06T01:22:41.740151Z | 2025-09-06T01:22:49.067315Z |
|--------------|--------------------------------|---------|----------------------------------------|--------------------------------------|-----------------------------|-----------------------------|

⭐ us on GitHub and join our community!