Providers
Providers
Reference documentation for each built-in provider. Every page documents the provider’s source string, its configuration schema, and every action it supports.
postgres— PostgreSQL data operationsmysql— MySQL and MariaDB data operationssqlite— SQLite data operationsredis— Redis and Valkey keys, hashes and commandss3— S3, S3-compatible stores and Google Cloud Storagegrpc— unary gRPC calls, with no generated codehttp— HTTP request providerexec— Shell command execution- External providers — using custom providers from separate binaries
To build your own provider, see Extending Orchard.
Reading a provider page
Each page follows the same layout:
- Source — the string you put in
required_providers. - Provider configuration — every attribute accepted by the
provider "name" { }block, with type, default, and whether it’s required. - Actions — one section per action type the provider handles, documenting attributes, outputs, and runtime behavior.
- Example — a complete, working scenario fragment you can adapt.
Types are written using Orchard’s HCL type expressions: string, number, bool,
list(string), map(string), object({ key = type, ... }), or any. See
expressions for the full type grammar.