Resources are the infrastructure components that pragma-os manages: storage buckets, datasets, secrets, and more. You declare resources in YAML, and pragma-os handles provisioning, state tracking, and lifecycle management.
Resource Structure
Every resource has a consistent structure:
| Field | Description | Example |
|---|
provider | The provider that manages this resource | gcp |
resource | The type of resource | storage |
name | A unique identifier you assign | data-lake |
config | Your settings for this resource | location: EU |
depends_on | What it connects to | Other resources |
outputs | What it exposes to other resources | URLs, IDs, secrets |
Configuration Example
Here’s a GCP storage bucket resource:
provider: gcp
resource: storage
name: data-lake
config:
location: EU
storage_class: STANDARD
# After provisioning, outputs become available:
# outputs:
# bucket_url: "gs://pragma-data-lake-abc123"
# self_link: "https://www.googleapis.com/storage/v1/b/pragma-data-lake-abc123"
Resource Lifecycle
Resources move through these states as pragma manages them:
| State | Description |
|---|
draft | Created but not yet queued for processing (use --draft flag) |
pending | Queued for provider to handle (default behavior) |
processing | Currently being handled by the provider |
ready | Successfully provisioned and operational |
failed | Processing failed, error recorded |
Updates and deletes reuse the same state flow: the resource transitions from ready → pending → processing → ready (or failed).
Dependencies
Resources can depend on other resources. When you reference another resource’s outputs, pragma automatically tracks the dependency:
provider: gcp
resource: bigquery_dataset
name: analytics
config:
location: EU
---
provider: gcp
resource: bigquery_table
name: events
config:
dataset: ${gcp.bigquery_dataset.analytics.dataset_id}
schema:
- name: event_id
type: STRING
- name: timestamp
type: TIMESTAMP
Applying Resources
Create and provision resources immediately:
pragma resources apply warehouse.yaml
pragma resources apply --draft warehouse.yaml
Next Steps
