fix(deps): update terraform dependencies #161
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
terraform-ibm-modules-ops
requested review from
daniel-butler-irl and
vbontempi
as code owners
|
/run pipeline |
terraform-ibm-modules-ops
force-pushed
the
renovate/terraform-dependencies
branch
from
9444e14 to
7ff22e5
Compare
|
/run pipeline |
terraform-ibm-modules-ops
force-pushed
the
renovate/terraform-dependencies
branch
from
7ff22e5 to
042d1e8
Compare
terraform-ibm-modules-ops
changed the title
|
/run pipeline |
terraform-ibm-modules-ops
force-pushed
the
renovate/terraform-dependencies
branch
from
042d1e8 to
1498104
Compare
terraform-ibm-modules-ops
force-pushed
the
renovate/terraform-dependencies
branch
from
1498104 to
9f987ee
Compare
|
/run pipeline |
terraform-ibm-modules-dev
approved these changes
Jul 24, 2025
Contributor
Author
|
🎉 This PR is included in version 2.1.6 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.37.1->2.38.03.52.3->3.53.01.6.3->1.6.41.4.0->1.4.11.1.6->1.1.74.6.7->4.7.0Release Notes
hashicorp/terraform-provider-kubernetes (kubernetes)
v2.38.0Compare Source
ENHANCEMENTS:
sub_path_exprto volume mount options pod spec [GH-2622]BUG FIXES:
data_source/kubernetes_pod_v1: fix an issue when the provider cuts out toleration under pod spec(spec.toleration) if it uses a well-known taint. [GH-2380]data_source/kubernetes_pod: fix an issue when the provider cuts out toleration under pod spec(spec.toleration) if it uses a well-known taint. [GH-2380]resource/kubernetes_cron_job: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_cron_job_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_daemon_set_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_daemonset: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_deployment: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_deployment_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_job: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_job_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_replication_controller_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_replication_controller: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_stateful_set: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]resource/kubernetes_stateful_set_v1: fix an issue when the provider cuts out toleration under pod spec template(*.template.spec.toleration`) if it uses a well-known taint. That could lead to a perpetual diff behavior. [GH-2380]NOTES:
kubernetes_deployment_v1,kubernetes_stateful_set_v1, etc, and now the provider will keep all tolerations(spec.toleration) returned by Kubernetes. The same is applicable for the data sourceskubernetes_pod_v1andkubernetes_pod. The behavior of resourceskubernetes_pod_v1andkubernetes_podremains unchanged, i.e. the provider will keep removing tolerations with well-known taints since they might be attached to the object by Kubernetes controller and could lead to a perpetual diff. [GH-2380]terraform-ibm-modules/terraform-ibm-base-ocp-vpc (terraform-ibm-modules/base-ocp-vpc/ibm)
v3.53.0Compare Source
Features
- The "Fully configurable" variation now deploys a cluster with a public endpoint enabled by default. This can be toggled using the
disable_public_service_endpointinput.- If VPC DA is selected (it is by default), there is now an option to configure the network ACLs. By default, it will create ACLs to allow public (port 80 and 443) so the Openshift console can be reached.(#740) (d60279f)
v3.52.4Compare Source
Bug Fixes
prefixinput variable in the DA to allownull(#739) (f12fb46)terraform-ibm-modules/terraform-ibm-secrets-manager-private-cert-engine (terraform-ibm-modules/secrets-manager-private-cert-engine/ibm)
v1.6.4Compare Source
Bug Fixes
prefixinput variable in the DA to allownull(#347) (feef9fb)terraform-ibm-modules/terraform-ibm-secrets-manager-private-cert (terraform-ibm-modules/secrets-manager-private-cert/ibm)
v1.4.1Compare Source
Bug Fixes
prefixinput variable in the DA to allownull(#333) (fcb5421)terraform-ibm-modules/terraform-ibm-secrets-manager-public-cert-engine (terraform-ibm-modules/secrets-manager-public-cert-engine/ibm)
v1.1.7Compare Source
Bug Fixes
prefixinput variable in the DA to allownull(#254) (72bf528)terraform-ibm-modules/terraform-ibm-vpe-gateway (terraform-ibm-modules/vpe-gateway/ibm)
v4.7.0Compare Source
Features
- removed input variable for DA solution for reserved_ips
- adjusted DA documentation and adopter usage (7a2387a)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.