terraform-provider-portainer Updates & Release Notes

Follow

10 updates curated from 1 source by the Releasebot Team. Last updated: Sep 2, 2026

Get this feed:
  • Aug 2, 2026
    • Date parsed from source:
      Aug 2, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.34.3

    terraform-provider-portainer releases v1.34.3 bug fixes for stack active state persistence and correct Docker Edge Agent creation.

    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).

    Original source
  • Jul 30, 2026
    • Date parsed from source:
      Jul 30, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.34.2

    terraform-provider-portainer fixes two Edge Agent issues in portainer_environment, improving public IP handling and address drift.

    Release v1.34.2

    Fixed

    Two Edge Agent fixes in portainer_environment:

    • public_ip was never sent to Portainer for Edge Agent environments (#137)
    • environment_address drifted from https://host to host on every plan (#136)
    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Portainer and hundreds of other software products.

    Create account
  • Jul 26, 2026
    • Date parsed from source:
      Jul 26, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.34.0

    terraform-provider-portainer releases v1.34.0 with proxy support, new Portainer 2.43 STS Git stack compatibility, and a fix for Git stack deployments, plus internal maintenance and stronger test coverage.

    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%.

    Original source
  • Jul 24, 2026
    • Date parsed from source:
      Jul 24, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.34.1

    terraform-provider-portainer releases v1.34.1 with a key bug fix for portainer_stack so active = false now stops new stacks right after deployment. It also adds internal maintenance improvements, faster parallel e2e CI, schema-doc drift checks, and updated documentation for missing fields.

    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.
    Original source
  • Jul 1, 2026
    • Date parsed from source:
      Jul 1, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.33.0

    terraform-provider-portainer ships v1.33.0 with Kubernetes brownfield adoption, adding import plus drift and deletion detection for all 17 Kubernetes resources. It also fixes portainer_stack deployment issues and updates the MongoDB driver dependency.

    Release v1.33.0

    Highlights

    Kubernetes brownfield adoption - terraform import and drift/deletion detection are now available for all 17 Kubernetes resources.

    Fix: portainer_stack Kubernetes deployments no longer fail with Object not found (key=0) after a successful create (#130).

    Added

    Read + Importer implemented for all 17 Kubernetes resources: application, clusterrole, clusterrolebinding, configmap, cronjob, helm, ingress, job, namespace, namespace_system, role, rolebinding, secret, service, serviceaccount, storage, volume. This enables importing existing infrastructure and detects out-of-band deletion (404 → resource is recreated on the next plan). A shared k8sConfirmExistsByGET helper backs the 13 manifest-based resources.

    Fixed

    portainer_stack with deployment_type = "kubernetes" failed during the finalize step with 404 Object not found (key=0) when Portainer's create response did not include a usable stack Id (observed on Portainer 2.21.x). The provider now resolves the real stack ID by name + endpoint before finalizing.

    Changed

    Bump go.mongodb.org/mongo-driver 1.17.6 -> 1.17.7.

    Upgrade notes

    Read for the Kubernetes resources intentionally does not refresh the authored manifest / values / spec fields (the K8s API returns server-expanded objects that would cause permanent diffs and, since Update is delete+recreate, churn workloads). After terraform import, set those fields in config to match the live object, otherwise the next apply will recreate it.

    Per-resource import IDs and the fields you must set are documented in each resource's docs page.

    Original source
  • Similar to terraform-provider-portainer with recent updates:

  • Jun 15, 2026
    • Date parsed from source:
      Jun 15, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.32.0

    terraform-provider-portainer ships v1.32.0 with safer imports and state handling, fixing edge stack brownfield imports, git ref updates in place, and docker secret refresh drift. It also modernizes CRUD and context handling, boosts linting and tests, and updates the Go toolchain.

    Release v1.32.0

    Bug fixes

    edge_stack: non-destructive brownfield import. Read now populates the full state from GET /edge_stacks/{id} (git config, edge groups, deployment metadata, AutoUpdate/webhook fields) instead of only ~6 of ~20 returned fields, so terraform import no longer forces a destroy + recreate. repository_reference_name is no longer ForceNew (the git endpoint updates it in place); other git fields keep ForceNew. Verified live: import now yields No changes, and a ref-name change plans as ~ update in-place.

    docker_secret: stable driver/templating on refresh. Read now flattens the API's {Name, Options} shape back into the flat map schema, fixing a refresh-time type error and state drift.

    Internal modernization & quality (no breaking config changes)

    Migrated all resources and data sources to context-aware CRUD (CreateContext/ReadContext/UpdateContext/DeleteContext returning diag.Diagnostics).

    HTTP requests now honor Terraform's context (cancellation / timeouts) via http.NewRequestWithContext.

    Importer.State → StateContext (dropped deprecated ImportStatePassthrough) and removed the -SA1019 staticcheck suppression.

    Re-enabled errcheck on d.Set so schema-mapping bugs surface instead of being silently ignored.

    Enabled 9 additional golangci-lint linters and fixed the fallout.

    Raised unit-test coverage 66% → ~78% (+350 tests).

    Bumped Go toolchain to 1.26.4 (resolves govulncheck GO-2026-5037 / GO-2026-5039).

    Original source
  • Jun 1, 2026
    • Date parsed from source:
      Jun 1, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.31.1

    terraform-provider-portainer fixes portainer_environment creation with tag_ids against Portainer v1.24.0+

    Release 1.31.1

    Fixed

    Creating a portainer_environment with tag_ids set failed against any Portainer version since v1.24.0

    Original source
  • May 31, 2026
    • Date parsed from source:
      May 31, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.31.0

    terraform-provider-portainer fixes Portainer API errors to show the actual response body.

    Release 1.31.0

    Fixed

    Errors from the Portainer API now include the actual response body instead of generic SDK placeholders like endpointCreateBadRequest. (#122 )

    Original source
  • May 27, 2026
    • Date parsed from source:
      May 27, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.30.0

    terraform-provider-portainer releases 1.30.0 with fixes for broken resources, newly sensitive credential fields, and refreshed Go and dependency versions. It also improves security, expands documentation, and adds more examples across resources and data sources.

    Release 1.30.0

    Fixes three broken resources, marks credential fields as sensitive, and updates the Go toolchain and dependencies.

    Action required

    Several token/credential fields are now Sensitive. If you expose any of them in an output, add sensitive = true or terraform apply will fail:

    portainer_user.api_key_raw

    portainer_webhook.token (resource and data source)

    portainer_webhook_execute.token

    portainer_cloud_credentials.credentials

    portainer_settings → oauth_settings.kube_secret_key

    output "generated_api_key" {
    value = portainer_user.ci.api_key_raw
    sensitive = true # now required
    }
    

    No state migration needed - values stay in state, just masked in CLI output.

    Bug fixes

    portainer_edge_configurations: fix "Missing form data value" on update against Portainer 2.39+ (correct multipart form fields). (#119)

    portainer_shared_git_credential: fix create always failing with HTTP 500 ... key=0 (response envelope is now unwrapped). (#120)

    portainer_open_amt: fix a doubled endpoint URL that prevented the resource from working.

    Security & dependencies

    Resolve all govulncheck findings (Go stdlib + golang.org/x/net).

    Build with Go 1.26.3; bump terraform-plugin-sdk/v2 to v2.40.1 and refresh go-cty, go-openapi, and golang.org/x/net.

    Documentation & examples

    Added an Import section to every importable resource's docs page.

    Populated a description for every schema attribute (resources and data sources), improving the generated registry documentation.

    Added example projects for every data source and the remaining resources.

    Original source
  • May 1, 2026
    • Date parsed from source:
      May 1, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Portainer logo

    terraform-provider-portainer by Portainer

    v1.29.0

    terraform-provider-portainer releases 1.29.0 with edge configuration fixes and automatic re-upload on file changes.

    Release 1.29.0

    Fixed

    portainer_edge_configurations: provider no longer adopts a pre-existing edge configuration when a same-name resource is created (#115)

    Added

    portainer_edge_configurations: detect changes to the underlying file at file_path via new computed file_sha256 attribute - re-upload is now triggered automatically when the file's contents change (#116)

    Original source

This is the end. You've seen all the release notes in this feed!

Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.