Six new resources, all backed by endpoints that did not exist before v0.30.0
and verified end-to-end against a live v0.30.2 instance:
dokploy_network Docker networks, now first-class. Services attach
through network_ids, which is what deprecates
Compose's isolated_deployment upstream.
dokploy_dns_provider Cloudflare or Route53, so adding a domain creates
its DNS record.
dokploy_vault_provider Env values resolved from HashiCorp Vault, Infisical,
AWS, Doppler, Azure or Scaleway at deploy time, so
the secret never lands in Dokploy or in state.
dokploy_schedule Cron jobs in a container, a stack, or on a server.
dokploy_volume_backup Scheduled backups of a named volume — the companion
to a mount that persists.
dokploy_libsql The sixth managed database engine.
libsql.create is the strictest endpoint in the API: eleven keys required to
be present, several only meaningfully null, no generated service name, and it
returns `true` rather than the row. CreateDefaults and ListIDs absorb all
three so the resource behaves like every other database.
Also filled the gaps a field-by-field diff against the live schema turned up:
domain gains `enabled` (the v0.30.0 park-a-domain toggle), compose gains
create_env_file, icon and service_networks, application gains icon and
preview_require_collaborator_permissions, and mounts accept libsql.
DNS and vault credentials are masked by Dokploy on read, so `config` is
tagged noread and keeps the configured value, as the basic-auth password
already does.
1.9 KiB
1.9 KiB
page_title, subcategory, description
| page_title | subcategory | description |
|---|---|---|
| dokploy_dns_provider Resource - dokploy | A DNS provider connection Dokploy uses to create records for domains automatically. config is a JSON object whose shape depends on providerType: # Cloudflare config = jsonencode({ providerType = "cloudflare", apiToken = var.cloudflare_token }) # AWS Route53 config = jsonencode({ providerType = "route53" accessKeyId = var.aws_access_key_id secretAccessKey = var.aws_secret_access_key }) ~> Dokploy masks the credentials when reading a provider back, so Terraform keeps the value you configured. Drift in config is not detected. |
dokploy_dns_provider (Resource)
A DNS provider connection Dokploy uses to create records for domains automatically.
config is a JSON object whose shape depends on providerType:
# Cloudflare
config = jsonencode({ providerType = "cloudflare", apiToken = var.cloudflare_token })
# AWS Route53
config = jsonencode({
providerType = "route53"
accessKeyId = var.aws_access_key_id
secretAccessKey = var.aws_secret_access_key
})
~> Dokploy masks the credentials when reading a provider back, so Terraform keeps the value you configured. Drift in config is not detected.
Schema
Required
config(String, Sensitive) Provider credentials as a JSON object, including theproviderTypediscriminator.name(String) Name of the connection. Must be unique within the organization and may contain only letters, digits,-and_.
Read-Only
created_at(String) RFC 3339 timestamp of when the connection was created.id(String) Unique DNS provider identifier.organization_id(String) Organization that owns the connection.provider_type(String) Provider kind derived fromconfig:cloudflareorroute53.