Terraform/OpenTofu modules

Relevant tools: Terraform, OpenTofu

If you have existing TF modules for maintaining your target resources via IaC, your module maintenance processes may continue normally.

Integrations overview #

The Orchestrator plays a central part in your Internal Developer Platform by being the go-to place for managing deployments and providing insights into deployment and rollout states of applications and infrastructure.

Orchestrator integrations can be structured along the core aspects represented by each box in the big picture below, with popular tools serving each aspects.

Terraform/OpenTofu modules #

For brevity, we will be using the term “TF” to refer to the combination “Terraform or OpenTofu” throughout this page.

A core part of integration is making these modules available to the Orchestrator. You do that by configuring modules referencing the existing TF module sources, usually in a Git repository on GitHub, GitLab, Bitbucket, Azure DevOps, Launchpad, or any other git hosting service:

resource "platform-orchestrator_module" "my_module" {
  module_source = "git::https://my-git-repos.com/path/to/repo//path/to/module?ref=vX.Y.Z"
  # ...
}

The Orchestrator then performs deployments by assembling a set of TF modules provided by you in this way, and applying them to the target infrastructure.

We recommend maintaining all Orchestrator configuration, including modules, via IaC using Humanitec’s own platform-orchestrator TF provider as shown.

Refer to module source locations for details on referencing modules from different locations and using specific module versions.