Resources

A resource is a structured, reusable object that holds everything a workflow needs to connect to an external system — a database, an object store, a SaaS API. Instead of scattering hostnames, ports, and credentials across many nodes, you define a resource once and reference it.

Resource types

Every resource has a resource type that defines its shape as a schema. For example, a postgresql resource type requires host, port, user, dbname, and a password secret field. Defining the type lets the editor validate resources and offer autocomplete.

Field kind	Stored as
Plain config (host, port, region)	Variable — readable
Credentials (password, token)	Secret — encrypted, write-only

Defining a resource

Resources live at a path. Scaffold one locally, fill in its spec, then deploy:

orvanta resource new f/folder/prod_db
# edit the generated spec, then:
orvanta sync push

Inspect or list resources with orvanta resource get <path> and orvanta resource list.

Using a resource in a workflow

Reference the resource by its path from a script or flow step; Orvanta resolves the fields (decrypting any secret fields) at execution time.

This keeps connection details consistent across every workflow that talks to the same system, and means rotating a credential is a single update.

Related

• Variables and secrets — The building blocks resources are made of.
• Workflows — Where resources are referenced.
• Roles and permissions — Restrict who can use a resource.