Releases: hckhanh/pulumi-any-terraform
[email protected]
[email protected]
Minor Changes
-
72aa8c6: ## v1.16.0 – Add write-only (_wo) ephemeral secret support
Features
- Added
_wo(write-only) attributes for ephemeral secrets across multiple resources. - Introduced
_wo_versionflag for rotation and re-creation of ephemeral-sensitive data.
Updated Resources
portainer_stackportainer_docker_secret
Documentation
- Extended examples for ephemeral secret usage.
- Updated resource docs with
_woattribute descriptions and usage notes.
- Added
🚀 Features
-
New Features (3929fef)
- Added new resource
portainer_deploy - Automates image updates and environment variable synchronization for stacks in Portainer (Swarm & Standalone).
- Added new resource
portainer_check - Enables validation of running containers or services after deployment with retries and state checks.
- Enhanced documentation
- Updated README and added detailed examples for CI/CD automation using new resources.
Improvements
- Added comprehensive Terraform examples for end-to-end automation (pull → deploy → exec → check).
- Fixed and unified documentation structure across all resources.
- Added new resource
❤️ Thank You
- Khánh Hoàng @hckhanh
[email protected]
[email protected]
Patch Changes
-
72aa8c6: ## What's Changed
- U-7085 [monitor] Set strict defaults for parameters essential for monitoring by @PetrHeinz in BetterStackHQ/terraform-provider-better-uptime#172
Full Changelog: BetterStackHQ/terraform-provider-better-uptime@v0.20.3...v0.20.4
🩹 Fixes
- Add
"sideEffects": falseto the package.json to indicate the package is side-effect-free (a5e20a3)
❤️ Thank You
- Khánh Hoàng @hckhanh
[email protected]
1.15.0 (2025-10-29)
🚀 Features
-
New Features (3929fef)
- Added new resource
portainer_deploy - Automates image updates and environment variable synchronization for stacks in Portainer (Swarm & Standalone).
- Added new resource
portainer_check - Enables validation of running containers or services after deployment with retries and state checks.
- Enhanced documentation
- Updated README and added detailed examples for CI/CD automation using new resources.
Improvements
- Added comprehensive Terraform examples for end-to-end automation (pull → deploy → exec → check).
- Fixed and unified documentation structure across all resources.
- Added new resource
❤️ Thank You
- Khánh Hoàng @hckhanh
[email protected]
[email protected]
0.11.0 (2025-10-28)
🚀 Features
-
Backwards compatibility break (577fc2a)
The resource
compute_container_appnow uses a list type to definecontainer,endpointandenvblocks. While both set and list types are compatible at the state level, this change has some limitations:Limitations
container,endpointandenvblocks have to sorted byname. You'll need to follow the same order on your .tf files, otherwise terraform will show them as modified after anapply;- Renaming a
container,endpointorenvwill cause the plan to show unrelated items being modified, as their order jumps up or down. We recommend deleting the block, applying, and then adding the block again with the new name; - Renaming an
endpointof type CDN might cause pullzones to be recreated, even if they aren't directly affected;
Upgrade path
- Make sure
terraform planreports no changes; - Upgrade the bunny.net provider;
- Sort the
container,endpointandenvblocks in your .tf files; - Add
version = 2to yourbunnynet_compute_container_appresources; - Run
terraform plan, it should report no changes apart from theversionattribute;
Motivation
While the set type would be the semantically correct type to use for those blocks, Terraform's implementation is neither complete nor uses the same internal details as the List type. This means that changing attributes in a sub-block often causes the entire
containerto be replaced, causing endpoints to be re-created, including their pullzones. It is also not possible to reference set objects inlifecycle.ignore_changes.
❤️ Thank You
- Khánh Hoàng @hckhanh
[email protected]
[email protected]
1.13.4 (2025-10-15)
🩹 Fixes
-
-
Resolved issue with
portainer_docker_configresource causing "invalid config version" errors when updating data. (0cfb194) -
Fixed prune option not working on stack create for repository-based stacks (now performs automatic redeploy with prune=true).
-
❤️ Thank You
- Khánh Hoàng @hckhanh