usr_unknown/terraform-provider-dokploy

Fork 0

Files

T

max-voitcov 2d1caf6e73

build / build (push) Successful in 3m56s

Details

release / release (push) Successful in 15m2s

Details

Cover what Dokploy v0.30 added

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.

2026-08-26 00:40:27 +03:00

2.1 KiB

Raw Blame History

page_title, subcategory, description

page_title	subcategory	description
dokploy_network Resource - dokploy		A Docker network managed by Dokploy. Attach services to it with network_ids on dokploy_application, dokploy_compose and the database resources. Every service also joins the shared dokploy-network unless detach_dokploy_network is set. ~> Docker networks are immutable. Dokploy has no update endpoint, so changing any attribute replaces the network — which detaches the services currently using it until they redeploy.

dokploy_network (Resource)

A Docker network managed by Dokploy.

Attach services to it with network_ids on dokploy_application, dokploy_compose and the database resources. Every service also joins the shared dokploy-network unless detach_dokploy_network is set.

~> Docker networks are immutable. Dokploy has no update endpoint, so changing any attribute replaces the network — which detaches the services currently using it until they redeploy.

Schema

Required

name (String) Name of the Docker network.

Optional

attachable (Boolean) Allow standalone containers to attach to an overlay network.
driver (String) Network driver. Use overlay for multi-node Swarm clusters and bridge for a single host. Valid values: bridge, overlay.
enable_ipv4 (Boolean) Enable IPv4 address allocation.
enable_ipv6 (Boolean) Enable IPv6 address allocation.
internal (Boolean) Isolate the network from external access.
ipam (String) Custom IP address management, as a JSON object with subnet, gateway and ipRange keys. Leave unset to let Docker choose a subnet.
mtu (Number) Maximum transmission unit for the network. Leave unset to use Docker's default.
server_id (String) Remote server to create the network on. Omit to use the Dokploy host itself.

Read-Only

created_at (String) RFC 3339 timestamp of when the network was created.
id (String) Unique network identifier.
organization_id (String) Organization that owns the network.

2.1 KiB Raw Blame History