skip to content
wihan.dev
view as markdown
browse the dokploy docs

dokploy_project (Data Source)

Look up a Dokploy project by id or by exact name.

Example Usage

terraform
data "dokploy_project" "example" {
  name = "my-project"
}

Schema

Optional

  • id (String) Project id. Set exactly one of id or name.
  • name (String) Exact project name. The lookup errors when zero or many projects match.

Read-Only

  • created_at (String) Creation timestamp.
  • description (String) Project description.
  • env (String, Sensitive) Variables that each service in the project can reference, exactly as Dokploy stores them. The attribute is sensitive because it usually holds credentials that this provider did not write. The plan output redacts it, but the state stores it in plain text, like all Terraform data.
  • environments (Attributes List) Environments in this project. (see nested schema for environments)
  • production_environment_id (String) Id of the default environment. Dokploy creates it with the project and names it production. The provider selects it with the server’s isDefault flag, not by name, so a rename does not change the value. Use it as the environment_id of a service in the default environment.
  • tag_ids (Set of String) Ids of the tags that the project carries. Empty when it has none.

Nested Schema for environments

Read-Only:

  • id (String) Environment id.
  • name (String) Environment name.