Terraform Provider Portainer Updates & Release Notes

v2.0.1

Fixed

• Stacks left in Error can be updated again (#147) A stack whose deployment had failed refused every further apply, in a fraction of a second and without sending a request. The only way out was starting the stack by hand in the Portainer UI. Fixing the compose file and re-applying now recovers the stack. A deployment that this provider itself started and that fails is still reported as a failure.

• portainer_stack_delete_by_name now works at all Every call failed with 400 Invalid query parameter: namespace. Portainer requires a namespace query parameter that its API specification does not document, so the resource never sent it.

• portainer_registry_connection now works at all Every check failed with 400 Username and password are required. Portainer demands credentials for all registry types, including public ones, so the data source never reached the connection test it exists to run. GitHub registries (type = 8) are also accepted now; the type was capped at 7.

Action required

Both fixes add a required argument to something that could not have been in working use, so no running configuration changes behaviour - but configurations that reference these two will now fail at plan time until they are updated:

resource "portainer_stack_delete_by_name" "example" {
  name        = "legacy-app" …

Release v2.0.0

Business Edition API coverage

This release roughly doubles what the provider can manage: 81 new resources and data sources covering the Business Edition API, alongside fixes for a stack deployment failure on Portainer 2.45 and a blocker that prevented Edge Agent environments from being created at all.

Nothing was removed or renamed. Every configuration valid on v1.35.0 is still valid, but read "Behaviour changes" before upgrading - one of them can replace an environment.

Behaviour changes

Edge Agent environments are replaced when their address changes. Portainer bakes the address into the edge key when the environment is created and never regenerates it, so an in-place update never actually took effect. Until now the provider emitted a warning and reported success, leaving the running agent on the old address. It now forces replacement instead, which issues a new edge key and means the agent has to be redeployed with it.

This only triggers for environment types 4 and 7, only when the address really changed, and not when the difference is the URL scheme alone. That last exclusion matters: Portainer normalises endpoint.URL down to the bare host, so environments created by older provider versions hold a scheme-less address in state and would otherwise be replaced on every apply.

Run terraform plan against your edge environments before upgrading. …

Release v1.35.0

Support for Portainer 2.45.0 LTS, full coverage of the Portainer API, and two Edge Agent fixes.

The provider grows from 120 to 172 resources and data sources.

Portainer 2.45 support

2.45 introduced native Portainer APIs for Kubernetes alongside the kube-apiserver proxy. An audit of every route between 2.44.0 and 2.45.0 found the API delta is confined to the Kubernetes handler; everything else that changed upstream is internal refactoring with no payload change.

New resources:

• portainer_kubernetes_node_drain - drain a node with all six kubectl drain options (force, timeout, grace period, ignore DaemonSets, delete emptyDir data, disable eviction)
• portainer_kubernetes_deployment_scale - manage a deployment's replica count, with drift detection
• portainer_kubernetes_deployment_rollback - roll a deployment back to an earlier revision
• portainer_kubernetes_persistent_volume - pin a PersistentVolume's reclaim policy

New data sources: portainer_kubernetes_manifest_dry_run (validate manifests server-side before anything is applied), portainer_kubernetes_ingress_classes, portainer_kubernetes_resource_quotas, portainer_kubernetes_replicasets, portainer_kubernetes_deployments, portainer_kubernetes_pods, portainer_kubernetes_pod_logs.

Existing Kubernetes resources keep using the kube-apiserver proxy, so nothing changes for users on older Portainer versions.

GitOps …

Release v1.34.3

Bug Fixes

• portainer_stack: active = false now persists on repository stacks (#139) - the update path stopped the stack before the git redeploy, which restarted it, so active = false never took effect (perpetual true -> false diff). The stop now runs after the redeploy.
• portainer_environment: type = 4 creates a Docker Edge Agent, not Kubernetes (#140) - an Edge Agent create now sends ContainerEngine=docker, so Portainer provisions the requested Docker edge (type 4) instead of a Kubernetes edge (type 7).

Release v1.34.1

Bug Fixes

• portainer_stack: honor active = false on create (#134) — a stack created with active = false is now stopped right after deployment instead of coming up running. Previously the flag was only applied on update, so a new stack always started, and with ignore_changes = [active] it never stopped at all.

Internal / Maintenance

• Unify direct-HTTP call sites behind a single doJSON helper (auth + status + JSON decode) across 97 files, with typed API errors and 404 handling.
• Add a table-driven CRUD test harness (crudCase).
• Add a schema↔docs drift-check linter as a new CI guard.
• Parallelize the e2e CI pipeline (shared composite setup action + split docker/kubernetes/swarm, edge and ssl jobs).

Documentation

• Document previously-missing schema fields: portainer_edge_stack.always_clone, portainer_settings.black_listed_labels, portainer_settings.edge_portainer_url.

Release v1.34.0

Features

• Proxy support: the provider now honors the standard HTTP_PROXY / HTTPS_PROXY / NO_PROXY environment variables when connecting to the Portainer endpoint. No-op when unset, so existing setups are unaffected. (#131)
• portainer_stack: new source_id attribute for Portainer 2.43 STS, which replaced shared Git credentials with the Sources model. Both source_id (2.43+) and repository_git_credential_id (< 2.43) are sent, so one configuration works against old and new Portainer. (#132)

Fixes

• portainer_stack: deploying a Git stack against Portainer 2.43 STS no longer fails with "Password must be specified when authentication is enabled"; set source_id (or fall back to inline repository_username/password). (#132)

Internal / Maintenance

• Centralized duplicated auth-header and d.Set handling into shared helpers (setAuthHeader, setFields); no behavior change.
• Raised unit-test coverage from ~77% to 85%.