MySQL resource

MySQL resource

MySQL/MariaDB application data via raw SQL, brokered transactions, viat_gql and CRUD. It introspects one configured database; it does not inherit PostgreSQL’s multi-schema or audit capabilities.

Verified against stable Viat 1.1.0. Examples use synthetic values/provider stubs; they were not executed, connected to live services or used to send messages. Start with the resource overview.

Prerequisites and permissions

Provision the database and a role with the exact SELECT/write/DDL privileges needed; enable network access from all API nodes. Use a TLS-capable server when ssl:true.

Complete configuration fields

Required describes structural parsing; conditional provider/backend requirements, runtime defaults and limitations follow below. Use null only where the type allows it. Numeric storage bounds do not imply every value is operationally valid. Do not rely on unknown-key dropping to detect typos.

plain

Field	Type / allowed values	Required	Omitted default	Constraints	Meaning
plain.authz_tables	map<string, AuthzTableBinding>	no; may be conditional	{}	—	Exposed table → authorization type or {type,actions}; bound engines deny unbound tables.
plain.database	string	yes	—	—	Target business database, not the platform database.
plain.graphql_overlay	string / null	no; may be conditional	no explicit default; see rules	—	TOML overlay for the database GraphQL engine, not a GraphQL request.
plain.host	string	yes	—	—	Server hostname/IP, not a URL or credential.
plain.port	integer	yes	—	minimum: 0; format: “uint16”; 0–65535	TCP port. Explicitly supply it where required; TLS does not infer a port.
plain.ssl	boolean	no; may be conditional	false	—	Stored TLS preference; see the version-specific runtime limitations below.

AuthzTableBinding

Allowed shape/values: string / AuthzTableMapping.

A string is the authorization-type shorthand; an object uses AuthzTableMapping below. Map keys are exposed table names, not arbitrary database-qualified names.

AuthzTableMapping

Unknown keys are rejected.

Field	Type / allowed values	Required	Omitted default	Constraints	Meaning
AuthzTableMapping.actions	map<string, string>	no; may be conditional	{}	—	Implied read/create/update/delete → model action name; omitted entries retain their own name.
AuthzTableMapping.type	string	yes	—	—	Authorization-model type name in the long-form table binding.

secret

Field	Type / allowed values	Required	Omitted default	Constraints	Meaning
secret.password	string	yes	—	—	Account password/app password, never a plaintext config setting.
secret.user	string	yes	—	—	Database login, encrypted with the secret half.

Runtime rules, defaults and limits

host, database and secret.user must be nonblank. port is required (typically 3306; not a default). password is required as a string but may be empty if the server permits it. ssl defaults false: false selects Disabled, true selects Preferred (not Required) in MySQL connect options. Preferred may fall back to plaintext; this is not a strict TLS or certificate-verification guarantee. audit and graphql_schemas are explicitly rejected, even when copied from PostgreSQL. graphql_overlay is optional TOML, syntax-checked on save. authz_tables has the same type/action mapping and deny-unbound rule as PostgreSQL; it applies to GraphQL/CRUD, not raw SQL.

Permissions, identity and save semantics

Management API requires platform authentication and project membership. List/show require membership; create, PUT, PATCH, Test, refresh, copy and delete require an effective project Owner/Admin/Developer role; the lower-privilege operator role cannot write. Management access grants neither upstream privileges nor runtime s3/file/row-policy access. MCP exposes only its actual listed tools; a resource schema is not a full MCP CRUD interface.

• Create: POST /projects/{slug}/resources, body {name,folder?,kind,plain,secret}. name is 1–64 bytes without /; system is reserved. Omitted/empty folder means root; otherwise [A-Za-z0-9_-]+ segments, at most 8 levels/255 bytes, no leading/trailing/repeated /.
• Identity is project-local (folder,name), not a global bare name. Duplicate names may exist in different folders. Use /resources/{name}?folder=team to locate detail routes explicitly; CLI uses team/name. Script bare names resolve own folder, root, then globally unique name; qualify cross-folder references, using Python getattr(ctx.resources, "team/name") or TypeScript ctx.resources["team/name"], not a property chain.
• PUT fully replaces: resend correct kind, complete plain and all secret values to retain; show masks cannot recover them. PATCH fixes kind; omitted plain preserves it, supplied plain replaces the entire document (not a deep merge); secret overlays only supplied fields, retaining omitted fields. Folder moves recheck references at the new anchor.
• Clear an optional secret by explicit null (only nullable fields) or empty string (only fields allowing empty). Required/conditionally required fields cannot be cleared. To clear optional plain fields, send complete plain without them so defaults/absence take effect. Null is not universal and *** is never an old-secret value.
• $keep is a PATCH/repo sentinel only at top-level plain fields, retaining an existing server value even for numeric/boolean fields. It cannot initialize a new resource or missing field. Nested $keep is not a deep-merge instruction.
• Repo file resources/<folder>/<name>.yaml carries folder through its path, with a bare name inside. viat pull writes string $secret placeholders for secret fields; viat push removes them (also accepts legacy !secret tags) and PATCHes existing resources, never using markers as credentials. Safely supply real required secrets before creating a new resource; a placeholder cannot create credentials. Top-level allowed_authorizers is repo access-sync metadata, not something to insert into plain arbitrarily.

The $secret placeholder differs from a credential reference: {"$secret":"name"} names another secret resource in supported config/cloud positions; HTTP/GraphQL string headers use the entire "$secret:name" value. These are not plaintext credentials. Save/read/export retain references; use resolves them. Targets resolve relative to the consuming resource folder and must already exist with kind secret. No substring interpolation.

Public responses contain resource identifiers, kind, folder, plain and a secret summary, never secret values. Summary *** denotes declared fields, not proof every optional credential is populated. Plain is readable/exportable; secret uses the deployment encrypted backend. Published script/dependency code follows snapshot rules: uses is frozen unless (live), not blanket live on every run. Resource projection, broker operations and explicit live secret IO are different boundaries.

Script secret boundary

1.1.0 compatibility/security limitation: this kind’s active runtime projection still injects a credential-bearing connection URL into the worker, even though the recommended operations below are brokered and do not need it. Treat the script and its dependency tree as trusted with that credential. Do not log/return the resource or extract a URL into application code; prefer the brokered helpers and least-privilege upstream credentials. Encryption at rest and CRUD masking do not remove this worker exposure.

Minimal configuration: management API / CLI file

This create-request JSON is also valid YAML for resource.yaml and the real CLI command below. Domains/credentials are fixtures; replace them and satisfy prerequisites before real use. Never commit a file containing actual secrets.

{
  "name": "demo",
  "folder": "",
  "kind": "mysql",
  "plain": {
    "host": "mysql.example.test",
    "port": 3306,
    "database": "demo",
    "ssl": true
  },
  "secret": {
    "user": "demo_reader",
    "password": "fixture-password-not-a-credential"
  }
}

viat project select <slug>
viat resource create --file resource.yaml
viat resource show demo --json

Equivalent API: POST /projects/{slug}/resources, relative to the instance management API root, with the body above. Expect the saved public resource and masked summary, not echoed secrets; an existing fixture name conflicts with 409. For repo sync omit folder and put it in resources/demo.yaml; viat push synchronizes complete plain and non-placeholder secret fields. Saving does not prove every remote operation works.

SDK operations and examples

query(sql,params={}) returns {rows,affected}; execute returns only affected count. Python transaction() is a context manager; TypeScript transaction(async tx => …) commits on callback success. Both have graphql(document,variables={}), also on tx; its authorization scope is maintained inside the same transaction. Raw query/execute are unscoped. Named :parameters are bound; absent ones bind NULL, objects/lists bind JSON text. For membership use MySQL JSON functions, not PostgreSQL casts. A failed statement rolls back and poisons the brokered transaction.

Both complete scripts declare the same root resource demo. Use only an approved fixture run. Writes, sends, builds and deletion are not dry-run.

Python

# @resource demo
from viat import ctx

def main():
    return ctx.resources.demo.query("SELECT :n AS answer", {"n": 42})

TypeScript

// @resource demo
import { ctx } from "viat";

export async function main() {
  return await ctx.resources.demo.query("SELECT :n AS answer", { n: 42 });
}

Rust

The verified Rust surface uses generic ctx.resource(name).call(op,req) (library uses ctx.library), not invented Python-shaped methods. This shows the corresponding protocol operation and returns its raw result, which can differ from the composite example above.

// @resource demo
use serde_json::{json, Value};
use viat::{Ctx, Error};

fn main() {
    viat::serve(|ctx: &Ctx, _args: Value| -> Result<Value, Error> {
        ctx.resource("demo").call("sql_query", json!({"sql":"SELECT :n AS answer","params":{"n":42}}))
    });
}

Shell has JSON environment projection, not method-decorated ctx.resources; these methods are not shell functions. Binary programs can implement corresponding worker-protocol RPC, not automatically Python/TypeScript methods. The sql lane supports the four SQL kinds; viat_gql only PostgreSQL/MySQL/SQLite; graphql targets remote graphql; llm targets llm. Unsupported lane/kind combinations are not automatically adapted.

Expected result

SELECT returns a row with answer=42, with no application table required. Exact decimal values may be strings; check MySQL’s column type rather than assuming every number is a JavaScript number.

Test behavior and side effects

Opens a TLS-configured one-shot connection and runs SELECT 1, then GraphQL diagnostics. It does not test every table write privilege.

Management API: POST /projects/{slug}/resources/{name}/test?folder=; CLI: viat resource test demo. Inspect body ok: connection failures normally still return HTTP 200 {ok:false,error:"…"}, possibly with schema_warnings. Status alone is insufficient; CLI exits nonzero on failure. Run only after approving network/filesystem effects.

Common failures and recovery

resource.mysql.empty_host/empty_database/empty_user: complete the indicated field. resource.mysql.graphql_schemas_unsupported: remove the list and create one resource per database. audit_unsupported_kind: remove audit. Engine schema failures: fix overlay/bindings, then refresh. Database auth/TLS errors require correcting grants or certificates.

Management errors normally use {error,message}. DTO resource.<kind>.* identifiers often occur in the message of 400 bad_request, not the top-level error; they are not a universal enum returned by every runtime helper. For 401 restore platform auth, 403 check effective project role/runtime rules, 404 check folder/name, 409 resolve duplicate identity or resource_in_use references. Distinguish upstream refusals from platform refusals and determine whether work might already have applied before retrying.

Production pitfalls and cleanup

Keep transactions short; do all transactional work through tx, not the outer resource. After DDL use viat resource refresh demo. Resource deletion does not drop the database or revoke its login; preserve backups and rotate separately.

General removal: disable callers, proxy/CRUD targets and related triggers, migrate dependencies and retain required evidence; then use viat resource delete demo or DELETE on the detail route. For 409 resource_in_use rebind/remove named endpoint holders first; do not bypass references. Removing an asset is not revoking third-party credentials, deleting external data or undoing prior side effects.

Related resources and maintenance evidence

• PostgreSQL resource
• SQLite resource
• SQL Server resource
• Resource overview

Pinned contract: contracts/1.1.0/resources.json → resource.mysql。

Reviewed implementation (product-repository-relative paths): viat-core/src/types/resource.rs (KindSpec/Plain/Secret); viat-api/src/dto.rs (normalization/validation); viat-api/src/handlers/resources.rs (CRUD/Test); viat-runtime/src/resource_io.rs, resources_json.rs, python.rs, typescript.rs; viat-api/src/runner/broker.rs; viat-cli/src/main.rs and repo/resources.rs; viat-core/src/types/snapshot.rs.