-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency hashicorp/terraform to v1.8.4 #1896
Closed
Closed
Conversation
This file contains 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
Plan Result (aat)
|
hmcts-jenkins-a-to-c
bot
added
ns:am
prd:am
rel:am-org-role-mapping-service-pr-1896
labels
Apr 30, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
April 30, 2024 15:10
f5df814
to
7092172
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
April 30, 2024 15:57
7092172
to
f4b9554
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
May 2, 2024 21:31
f4b9554
to
324fdbd
Compare
Plan Result (prod)
|
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
3 times, most recently
from
May 8, 2024 09:39
e7df8e6
to
1bdd11a
Compare
renovate
bot
changed the title
Update dependency hashicorp/terraform to v1.8.2
Update dependency hashicorp/terraform to v1.8.3
May 8, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
2 times, most recently
from
May 9, 2024 10:36
bbe6a47
to
7a0f022
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
2 times, most recently
from
May 14, 2024 19:19
4e9727e
to
39b3eb3
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
May 20, 2024 16:11
39b3eb3
to
d086648
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
2 times, most recently
from
May 21, 2024 10:39
af13925
to
150e607
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
May 22, 2024 16:11
150e607
to
969b66d
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
May 22, 2024 19:07
969b66d
to
b4ccdd8
Compare
renovate
bot
changed the title
Update dependency hashicorp/terraform to v1.8.3
Update dependency hashicorp/terraform to v1.8.4
May 22, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
3 times, most recently
from
May 23, 2024 14:09
95334ff
to
37e8ec9
Compare
renovate
bot
force-pushed
the
renovate/hashicorp-terraform-1.x
branch
from
May 23, 2024 15:01
37e8ec9
to
cee5006
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
aat/no-changes
dependencies
Pull requests that update a dependency file
ns:am
prd:am
prod/no-changes
0 participants
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:
1.7.4
->1.8.4
Release Notes
hashicorp/terraform (hashicorp/terraform)
v1.8.4
Compare Source
1.8.4 (May 22, 2024)
BUG FIXES:
core
: Fix exponential slowdown in some cases when modules are usingdepends_on
. (#35157)import
blocks: Fix bug where resources with nested, computed, and optionalid
attributes would fail to generate configuration. (#35220)golang.org/x/net
release, which addressed CVE-2023-45288 (#35165)v1.8.3
Compare Source
1.8.3 (May 8, 2024)
BUG FIXES:
terraform test
: Providers configured within an overridden module could panic. (#35110)core
: Fix crash when a provider incorrectly plans a nested object when the configuration isnull
(#35090)v1.8.2
Compare Source
1.8.2 (April 24, 2024)
BUG FIXES:
terraform apply
: Prevent panic when a provider erroneously provides unknown values. (#35048)terraform plan
: Replace panic with error message when self-referencing resources and data sources from thecount
andfor_each
meta attributes. (#35047)terraform test
: RestoreTF_ENV_*
variables being made available to testing modules. (#35014)terraform test
: Prevent crash when referencing local variables within overridden modules. (#35030)ENHANCEMENTS:
OTHER CHANGES:
cloud
block and environment variables likeTF_CLOUD_ORGANIZATION
remain unchanged. (#35050)NOTE:
Starting with this release, we are including a copy of our license file in all packaged versions of our releases, such as the release .zip files. If you are consuming these files directly and would prefer to extract the one terraform file instead of extracting everything, you need to add an extra argument specifying the file to extract, like this:
v1.8.1
Compare Source
1.8.1 (April 17, 2024)
BUG FIXES:
moved
block: Fix crash when move targets a module which no longer exists. (#34986)import
block: Fix crash when generating configuration for resources with complex sensitive attributes. (#34996)v1.8.0
Compare Source
1.8.0 (April 10, 2024)
If you are upgrading from Terraform v1.7 or earlier, please refer to
the Terraform v1.8 Upgrade Guide.
NEW FEATURES:
Providers can now offer functions which can be used from within the Terraform configuration language.
The syntax for calling a provider-contributed function is
provider::provider_name::function_name()
. (#34394)Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type.
This extends the
moved
block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported.New
issensitive
function returns true if the given value is marked as sensitive.ENHANCEMENTS:
terraform test
: File-level variables can now refer to global variables. (#34699)When generating configuration based on
import
blocks, Terraform will detect strings that contain valid JSON syntax and generate them as calls to thejsonencode
function, rather than generating a single string. This is primarily motivated by readability, but might also be useful if you need to replace part of the literal value with an expression as you generalize your module beyond the one example used for importing.terraform plan
now uses a different presentation for describing changes to lists where the old and new lists have the same length. It now compares the elements with correlated indices and shows a separate diff for each one, rather than trying to show a diff for the list as a whole. The behavior is unchanged for lists of different lengths.terraform providers lock
accepts a new boolean option-enable-plugin-cache
. If specified, and if a global plugin cache is configured, Terraform will use the cache in the provider lock process. (#34632)built-in "terraform" provider: new
decode_tfvars
,encode_tfvars
, andencode_expr
functions, for unusual situations where it's helpful to manually generate or read from Terraform's "tfvars" format. (#34718)terraform show
's JSON rendering of a plan now includes two explicit flags"applyable"
and"complete"
, which both summarize characteristics of a plan that were previously only inferrable by consumers replicating some of Terraform Core's own logic. (#34642)"applyable"
means that it makes sense for a wrapping automation to offer to apply this plan."complete"
means that applying this plan is expected to achieve convergence between desired and actual state. If this flag is present and set tofalse
then wrapping automations should ideally encourage an operator to run another plan/apply round to continue making progress toward convergence.BUG FIXES:
iterator
argument within a dynamic block. (#34751)Previous Releases
For information on prior major and minor releases, see their changelogs:
v1.7.5
Compare Source
1.7.5 (March 13, 2024)
BUG FIXES:
Configuration
📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.