fix(deps): update required_provider to latest for deployable architectures #26
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.16.0->2.17.01.76.1->1.77.12.33.0->2.36.0Release Notes
hashicorp/terraform-provider-helm (helm)
v2.17.0Compare Source
ENHANCEMENT:
resource/helm_release: the dry-run option is now set toserverto execute any chart lookups against the server during the plan stage. [GH-1335]BUG FIXES:
resource/helm_release: fix an issue wherepostrender.argsis not parsed correctly. [GH-1534]v2.16.1Compare Source
BUG FIXES:
helm_release: Fix nil pointer deref panic on destroy when helm release is not found [GH-1501]IBM-Cloud/terraform-provider-ibm (ibm)
v1.77.1Compare Source
Enhancements
v1.77.0Compare Source
Enhancements
Bug Fixes
v1.76.3Compare Source
v1.76.2Compare Source
hashicorp/terraform-provider-kubernetes (kubernetes)
v2.36.0Compare Source
ENHANCEMENTS:
resource/kubernetes_secret_v1: Add support for write only attributes fordata_woandbinary_data_wo. [GH-2692]v2.35.1Compare Source
BUG FIXES:
resource/kubernetes_job_v1: revert the changes introduced in v2.34.0, wherettl_seconds_after_finishedwas set to0. [GH-2650]resource/kubernetes_daemon_set_v1: fix issue where fieldsspec.strategy.rolling_update.max_surgeandspec.strategy.rolling_update.max_unavailablewere not being validated correctly. [GH-2653]v2.35.0Compare Source
FEATURES:
resources_kubernetes_daemon_set_v1: Addedmax_surgeargument for torolling_updateblock. [GH-2630]v2.34.0Compare Source
ENHANCEMENTS:
conditionsattribute tokubernetes_nodesdata source, which will provide detailed node health and status information [GH-2612]kubernetes_secret_v1_dataresource to the kubernetes provider. This resource will allow users to manage kubernetes secrets [GH-2604]FEATURES:
kubernetes_certificate_signing_request_v1[GH-2628]kubernetes_token_request_v1[GH-2628]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.