This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
chore(deps): update hashicorp/terraform docker tag to v0.15.0 - autoclosed #309
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
Codecov Report
@@ Coverage Diff @@
## master #309 +/- ##
===========================================
+ Coverage 0 53.32% +53.32%
===========================================
Files 0 126 +126
Lines 0 5605 +5605
===========================================
+ Hits 0 2989 +2989
- Misses 0 2424 +2424
- Partials 0 192 +192
Continue to review full report at Codecov.
|
3d37cac
to
0ddd277
Compare
0ddd277
to
504fe5d
Compare
504fe5d
to
727c19e
Compare
727c19e
to
80c019f
Compare
80c019f
to
e392ec7
Compare
cf3386d
to
590ea54
Compare
590ea54
to
5cdc7d5
Compare
5cdc7d5
to
d2ad3ce
Compare
d2ad3ce
to
d167a10
Compare
d167a10
to
598730e
Compare
598730e
to
94dab43
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
0.11.14
->0.15.0
0.12.24
->0.15.0
Release Notes
hashicorp/terraform
v0.15.0
Compare Source
0.15.0 (April 14, 2021)
UPGRADE NOTES AND BREAKING CHANGES:
The following is a summary of each of the changes in this release that might require special consideration when upgrading. Refer to the Terraform v0.15 upgrade guide for more details and recommended upgrade steps.
"Proxy configuration blocks" (provider blocks with only
alias
set) in shared modules are now replaced with a more explicitconfiguration_aliases
argument within therequired_providers
block. Some support for the old syntax is retained for backward compatibility, but we've added explicit error messages for situations where Terraform would previously silently misinterpret the purpose of an emptyprovider
block. (#27739)The
list
andmap
functions, both of which were deprecated since Terraform v0.12, are now removed. You can replace uses of these functions withtolist([...])
andtomap({...})
respectively. (#26818)Terraform now requires UTF-8 character encoding and virtual terminal support when running on Windows. This unifies Terraform's terminal handling on Windows with that of other platforms, as per Microsoft recommendations. Terraform previously required these terminal features on all other platforms, and now requires them on Windows too.
UTF-8 and virtual terminal support were introduced across various Windows 10 updates, and so Terraform is no longer officially supported on the original release of Windows 10 or on Windows 8 and earlier. However, there are currently no technical measures to artificially prevent Terraform from running on these obsolete Windows releases, and so you may still be able to use Terraform v0.15 on older Windows versions if you either disable formatting (using the
-no-color
) option, or if you use a third-party terminal emulator package such as ConEmu, Cmder, or mintty.We strongly encourage planning to migrate to a newer version of Windows rather than relying on these workarounds for the long term, because the Terraform team will test future releases only on up-to-date Windows 10 and can therefore not guarantee ongoing support for older versions.
Built-in vendor provisioners (chef, habitat, puppet, and salt-masterless) have been removed. (#26938)
Interrupting execution will now cause terraform to exit with a non-zero exit status. (#26738)
The trailing
[DIR]
argument to specify the working directory for various commands is no longer supported. Use the global-chdir
option instead. (#27664)For example, instead of
terraform init infra
, writeterraform -chdir=infra init
.The
-lock
and-lock-timeout
options are no longer available onterraform init
(#27464)The
-verify-plugins=false
option is no longer available onterraform init
. (Terraform now always verifies plugins.) (#27461)The
-get-plugins=false
option is no longer available onterraform init
. (Terraform now always installs plugins.) (#27463)The
-force
option is no longer available onterraform destroy
. Use-auto-approve
instead (#27681)The
-var
and-var-file
options are no longer available onterraform validate
. These were deprecated and have had no effect since Terraform v0.12. (#27906)terraform version -json
output no longer includes the (previously-unpopulated) "revision" property (#27484)In the
gcs
backend thepath
config argument, which was deprecated since Terraform v0.11, is now removed. Use theprefix
argument instead. (#26841)The deprecated
ignore_changes = ["*"]
wildcard syntax is no longer supported. Useignore_changes = all
instead. (#27834)Previously deprecated quoted variable type constraints are no longer supported. Follow the instructions in the error message to update your type signatures to be more explicit. For example, use
map(string)
instead of"map"
. (#27852)Terraform will no longer make use of the
HTTP_PROXY
environment variable to determine proxy settings for connecting to HTTPS servers. You must always setHTTPS_PROXY
if you intend to use a proxy to connect to an HTTPS server. (Note: This affects only connections made directly from Terraform CLI. Terraform providers are separate programs that make their own requests and may thus have different proxy configuration behaviors.)Provider-defined sensitive attributes will now be redacted throughout the plan output. You may now see values redacted as
(sensitive)
that were previously visible, because sensitivity did not follow provider-defined sensitive attributes.If you are transforming a value and wish to force it not to be sensitive, such as if you are transforming a value in such a way that removes the sensitive data, we recommend using the new
nonsensitive
function to hint Terraform that the result is not sensitive.The
atlas
backend, which was deprecated since Terraform v0.12, is now removed. (#26651)We've upgraded the underlying TLS and certificate-related libraries that Terraform uses when making HTTPS requests to remote systems. This includes the usual tweaks to preferences for different cryptographic algorithms during handshakes and also some slightly-stricter checking of certificate syntax. These changes should not cause problems for correctly-implemented HTTPS servers, but can sometimes cause unexpected behavior changes with servers or middleboxes that don't comply fully with the relevant specifications.
ENHANCEMENTS:
required_providers
entry can now containconfiguration_aliases
to declare additional configuration aliases names without requirring a configuration block (#27739)one
for concisely converting a zero-or-one element list/set into a single value that might benull
. (#27454)sensitive
andnonsensitive
allow module authors to explicitly override Terraform's default infererence of value sensitivity for situations where it's too conservative or not conservative enough. (#27341)backend
block in a non-root module. Terraform has always ignored such declarations, but previously did so silently. This is a warning rather than an error only because it is sometimes convenient to temporarily use a root module as if it were a child module in order to test or debug its behavior separately from its main backend. (#26954)terraform fmt
now automatically fixes most cases that the warning would previously highlight. We still recommend using simpler expressions where possible, but the deprecation warning had caused a common confusion in the community that the interpolation syntax is always deprecated, rather than only in the interpolation-only case. (#27835)terraform init
: Will now make suggestions for possible providers on some registry failures, and generally remind ofrequired_providers
on all registry failures. (#28014)terraform init
: Provider installation will now only attempt to rewrite.terraform.lock.hcl
if it would contain new information. (#28230)terraform init
: New-lockfile=readonly
option, which suppresses writing changes to the dependency lock file. Any installed provider packages must already be recorded in the lock file, or initialization will fail. Use this if you are managing the lock file via a separate process and want to avoid adding new checksums for existing dependencies. (#27630)terraform show
: Improved performance when rendering large plans as JSON. (#27998)terraform validate
: The JSON output now includes a code snippet object for each diagnostic. If present, this object contains an excerpt of the source code which triggered the diagnostic, similar to what Terraform would include in human-oriented diagnostic messages. (#28057)terraform destory
instead ofdestroy
, will now print out a specific error message about the command being invalid, rather than just printing out the usual help directory. (#26967)TF_LOG_CORE
andTF_LOG_PROVIDER
(#26685)BUG FIXES:
defaults
function. (#27979, #28067)terraform validate
: Validation now ignores providers that lack configuration, which is useful for validating modules intended to be called from other modules which therefore don't include their own provider configurations. (#24896)terraform fmt
: Fixfmt
output when unwrapping redundant multi-line string interpolations (#28202)terraform console
: expressions usingpath
(path.root
,path.module
) now return the same result as they would in a configuration (#27263)terraform show
: Fix crash when rendering JSON plans containing iterable unknown values. (#28253)terraform show
: fix issue withchild_modules
not properly displaying in certain circumstances. (#27352)terraform state list
: fix bug where nested modules' resources were missing (#27268)terraform state mv
: fix display names in errors and improve error when failing to target a whole resource (#27482)terraform taint
: show resource name in -allow-missing warning (#27501)terraform untaint
: show resource name in -allow-missing warning (#27502)-input=false
. Previously Terraform would behave as if the user entered an empty string, which often led to confusing results. (#26509)TF_LOG
levels other thantrace
will now work reliably. (#26632)-refresh=false
. (#28272)terraform show saved.tfplan
matchesterraform plan
, and sensitive values are elided. (#28201)create_before_destroy
ordering is preserved. (#28228)EXPERIMENTS:
provider_sensitive_attrs
: This experiment has now concluded, and its functionality is now on by default. If you were previously participating in this experiment then you can remove the experiment opt-in with no other necessary configuration changes.terraform test
command, which is currently an experimental feature serving as part of the Module Testing Experiment.v0.14.10
Compare Source
0.14.10 (April 07, 2021)
BUG FIXES:
v0.14.9
Compare Source
0.14.9 (March 24, 2021)
BUG FIXES:
v0.14.8
Compare Source
BUG FIXES:
ENHANCEMENTS:
v0.14.7
Compare Source
0.14.7 (February 17, 2021)
ENHANCEMENTS:
target_platform
as"windows"
in theconnection
block. (#26865)BUG FIXES:
show -json
not outputting the full module tree when some child modules have no resources (#27352)required_providers
instead of provider config (#27697)v0.14.6
Compare Source
0.14.6 (February 04, 2021)
ENHANCEMENTS:
BUG FIXES:
init
will reuse installed providers rather than fetching the provider again (#27582)v0.14.5
Compare Source
0.14.5 (January 20, 2021)
ENHANCEMENTS:
BUG FIXES:
v0.14.4
Compare Source
0.14.4 (January 06, 2021)
UPGRADE NOTES:
BUG FIXES:
sensitive
values as arguments to data sources ([#27335])sensitive
values ascount
arguments on validate ([#27410])sensitive
values to module input variables which have custom variable validation ([#27412])sensitive
values ([#27420])v0.14.3
Compare Source
0.14.3 (December 17, 2020)
ENHANCEMENTS:
terraform output
: Now supports a new "raw" mode, activated by the-raw
option, for printing out the raw string representation of a particular output value. (#27212)Only primitive-typed values have a string representation, so this formatting mode is not compatible with complex types. The
-json
mode is still available as a general way to get a machine-readable representation of an output value of any type.config:
for_each
now allows maps whose element values are sensitive, as long as the element keys and the map itself are not sensitive. (#27247)BUG FIXES:
anytrue
andalltrue
functions when called with values which are not known until apply. (#27240)sum
function when called with values which are not known until apply. Also allowssum
to cope with numbers too large to represent in float64, along with correctly handling errors around infinite values. (#27249)count
expressions (#27238)sensitive
values with expressions and functions.coalescelist
with anull
argument (#26988)terraform apply
:-refresh=false
was skipped when running apply directly (#27233)terraform init
: setting-get-plugins
tofalse
will now cause a warning, as this flag has been a no-op since 0.13.0 and usage is better served through usingprovider_installation
blocks (#27092)terraform init
and other commands which interact with the dependency lock file: These will now generate a normal error message if the lock file is incorrectly a directory, rather than crashing as before. (#27250)v0.14.2
Compare Source
0.14.2 (December 08, 2020)
BUG FIXES:
terraform_remote_state
data source. This check is unnecessary, because the data source is read-only by definition. (#27197)v0.14.1
Compare Source
0.14.1 (December 08, 2020)
ENHANCEMENTS:
-ignore-remote-version
. (#26947)BUG FIXES:
ignore_changes
appears to not work, or causes validation errors with some resources. (#27141)terraform fmt
: Fix incorrect formatting with attribute expressions enclosed in parentheses. (#27040)v0.14.0
Compare Source
0.14.0 (December 02, 2020)
NEW FEATURES:
Terraform now supports marking input variables as sensitive, and will propagate that sensitivity through expressions that derive from sensitive input variables.
terraform init
will now generate a lock file in the configuration directory which you can check in to your version control so that Terraform can make the same version selections in future. (#26524)If you wish to retain the previous behavior of always taking the newest version allowed by the version constraints on each install, you can run
terraform init -upgrade
to see that behavior.Terraform will now support reading and writing all compatible state files, even from future versions of Terraform. This means that users of Terraform 0.14.0 will be able to share state files with future Terraform versions until a new state file format version is needed. We have no plans to change the state file format at this time. (#26752)
UPGRADE NOTES:
sensitive
, or attributes a provider defines assensitive
if theprovider_sensitive_attrs
experiment is activated) must also be defined as sensitive, or Terraform will error at plan.version
argument inside provider configuration blocks has been documented as deprecated since Terraform 0.12. As of 0.14 it will now also generate an explicit deprecation warning. To avoid the warning, use provider requirements declarations instead. (#26135)Transfer-Encoding: identity
. (#26357)terraform 0.13upgrade
subcommand and the associated upgrade mechanisms are no longer available. Complete the v0.13 upgrade process before upgrading to Terraform v0.14.debug
command, which did not offer additional functionality, has been removed.ENHANCEMENTS:
sensitive
argument for variable blocks, which supresses output where that variable is used (#26183)alltrue
andanytrue
functions, which serve as a sort of dynamic version of the&&
and||
or operators, respectively. These are intended to allow evaluating boolean conditions, such as in variablevalidation
blocks, across all of the items in a collection usingfor
expressions. (#25656], [#26498)textencodebase64
andtextdecodebase64
for encoding text in various character encodings other than UTF-8. (#25470)terraform plan
andterraform apply
: Added an experimental concise diff renderer. By default, Terraform plans now hide most unchanged fields, only displaying the most relevant changes and some identifying context. This experiment can be disabled by setting aTF_X_CONCISE_DIFF
environment variable to0
. (#26187)ignore_changes
can now apply to map keys that are not listed in the configuration (#26421)terraform console
: Now has distinct rendering of lists, sets, and tuples, and correctly renders objects withnull
attribute values. Multi-line strings are rendered using the "heredoc" syntax. (#26189, #27054)terraform login
: Added support for OAuth2 application scopes. (#26239)terraform fmt
: Will now do some slightly more opinionated normalization behaviors, using the documented idiomatic syntax. (#26390)terraform init
's provider installation step will now abort promptly if Terraform receives an interrupt signal. (#26405)-chdir=...
, placed before the selected subcommand, instructs Terraform to switch to a different working directory before executing the subcommand. This is similar to switching to a new directory withcd
before running Terraform, but it avoids changing the state of the calling shell. (#26087)terraform init
. (#26761)terraform plan
no longer uses a separate refresh phase. Instead, all resources are updated on-demand during planning (#26270)SSL_CERT_DIR
environment variable can now be a colon-separated list of multiple certificate search paths. (#26357)Security.framework
API to access the system trust roots, for improved consistency with other MacOS software. (#26357)BUG FIXES:
required_providers
object. (#26184)element()
is called with a negative offset (#26079)lookup()
will now only treat map as unknown if it is wholly unknown (#26427)terraform fmt
: Fix incorrect heredoc syntax in plan diff output (#25725)terraform show
: Hide sensitive outputs from display (#26740)terraform taint
: If the configuration'srequired_version
constraint is not met, thetaint
subcommand will now correctly exit early. (#26345)terraform taint
andterraform untaint
: Fix issue when usingtaint
(anduntaint
) with workspaces where statefile was not found. (#22467)terraform init
: Fix locksfile constraint output for versions like "1.2". (#26637)terraform init
: Omit duplicate version constraints when installing packages or writing locksfile. (#26678)state push -force
to work for all backends (#26190)/
(#25842)EXPERIMENTS:
Experiments are Terraform language features that are not yet finalized but that we've included in a release so you can potentially try them out and share feedback. These features are only available if you explicitly enable the relevant experiment for your module. To share feedback on active experiments, please open an enhancement request issue in the main Terraform repository.
module_variable_optional_attrs
: When declaring an input variable for a module whose type constraint (type
argument) contains an object type constraint, the type expressions for the attributes can be annotated with the experimentaloptional(...)
modifier.Marking an attribute as "optional" changes the type conversion behavior for that type constraint so that if the given value is a map or object that has no attribute of that name then Terraform will silently give that attribute the value
null
, rather than returning an error saying that it is required. The resulting value still conforms to the type constraint in that the attribute is considered to be present, but references to it in the recieving module will find a null value and can act on that accordingly.This experiment also includes a function named
defaults
which you can use in a local value to replace the null values representing optional attributes with non-null default values. The function also requires that you enable themodule_variable_optional_attrs
experiment for any module which calls it.provider_sensitive_attrs
: This is an unusual experiment in that it doesn't directly allow you to use a new feature in your module configuration but instead it changes the automatic behavior of Terraform in modules where it's enabled.For modules where this experiment is active, Terraform will consider the attribute sensitivity flags set in provider resource type schemas when propagating the "sensitive" flag through expressions in the configuration. This is experimental because it has the potential to make far more items in the output be marked as sensitive than before, and so we want to get some experience and feedback about it before hopefully making this the default behavior.
One important consequence of enabling this experiment is that you may need to mark more of your module's output values as
sensitive = true
, in any case where a particular output value is derived from a value a provider has indicated as being sensitive. Without that explicit annotation, Terraform will return an error to avoid implicitly exposing a sensitive value via an output value.If you try either of these features during their experimental periods and have feedback about them, please open a feature request issue. We are aiming to stabilize both features in the forthcoming v0.15 release, but their design may change in the meantime based on feedback. If we make further changes to the features during the v0.15 period then they will be reflected in v0.15 alpha releases.
v0.13.6
Compare Source
0.13.6 (January 06, 2021)
UPGRADE NOTES:
terraform_remote_state
data source no longer enforces Terraform version checks on the remote state file. This allows Terraform 0.13.6 to access remote state from future Terraform versions, up until a future incompatible state file version upgrade is required. (#26692)BUG FIXES:
-get-plugins
tofalse
will now cause a warning, as this flag has been a no-op since 0.13.0 and usage is better served through usingprovider_installation
blocks (#27092)v0.13.5
Compare Source
0.13.5 (October 21, 2020)
BUG FIXES:
v0.13.4
Compare Source
0.13.4 (September 30, 2020)
UPGRADE NOTES:
habitat
,puppet
,chef
, andsalt-masterless
are now deprecated and will be removed in a future version of Terraform. More information on Discuss."${foo}"
should be rewritten as justfoo
. (#27272] [#26334)BUG FIXES:
terraform providers schema
. This allows development tools such as the Terraform language server to offer autocompletion for the first resource for a given provider. (#26318)depends_on
, either directly or through their modules, are no longer are forced to wait until apply by other planned data source reads (#26375)v0.13.3
Compare Source
0.13.3 (September 16, 2020)
BUG FIXES:
state push -force
to work for all backends (#26190)v0.13.2
Compare Source
0.13.2 (September 02, 2020)
NEW FEATURES:
ENHANCEMENTS:
0.13upgrade
. If a provider in the Terraform Registry has moved to a new namespace, the0.13upgrade
subcommand now detects this and follows the redirect where possible. (#26061)init
error diagnostics when encountering what appears to be an in-house provider required by a pre-0.13 state file. Terraform will now display suggestedterraform state replace-provider
commands which will fix this specific problem. (#26066)BUG FIXES:
output
subcommand with no arguments results in no outputs. This aligns the UI to match the 0 exit code in this situation, which is notable but not necessarily an error. (#26036)v0.13.1
Compare Source
0.13.1 (August 26, 2020)
ENHANCEMENTS:
cidrsubnet
andcidrhost
now support address extensions of more than 32 bits (#25517)BUG FIXES:
module
blocks can now override the specialproviders
argument. (#25496)terraform console
andterraform import
commands. [#25454]-target
option toterraform plan
andterraform apply
now correctly handles addresses containing module instance indexes. (#25760)terraform state mv
can now move the last resource from a module without panicking. (#25523)terraform version
contains an outdated version notice, this is now printed after the version number and not before. (#25811)TF_WORKSPACE
environment variable, and allow any existing invalid workspaces to be deleted. (#25262)-no-color
flags are set on the command line. (#25847)-backend-config
override files with the enhanced remote backend. (#25960)dynamic
block producing an unknown number of blocks will no longer incorrectly produce the error "Provider produced inconsistent final plan" when the block type is backed by a set of objects. (#25662)terraform
provider. (#25861)terraform import
even if defaults are given for input variables (#25890)required_version
constraint diagnostics when multiplerequired_version
settings exist in a single module (#25898)v0.13.0
Compare Source
0.13.0 (August 10, 2020)
This section contains details about various changes in the v0.13 major release. If you are upgrading from Terraform v0.12, we recommend first referring to the v0.13 upgrade guide for information on some common concerns during upgrade and guidance on ways to address them. (The final upgrade guide and the documentation for the new features will be published only when v0.13.0 final is released; until then, some links in this section will be non-functional.)
NEW FEATURES:
count
andfor_each
for modules: Similar to the arguments of the same name inresource
anddata
blocks, these create multiple instances of a module from a singlemodule
block. (#24461)depends_on
for modules: Modules can now use thedepends_on
argument to ensure that all module resource changes will be applied after any changes to thedepends_on
targets have been applied. (#25005)Automatic installation of third-party providers: Terraform now supports a decentralized namespace for providers, allowing for automatic installation of community providers from third-party namespaces in the public registry and from private registries. (More details will be added about this prior to release.)
Custom validation rules for input variables: A new
validation
block type insidevariable
blocks allows module authors to define validation rules at the public interface into a module, so that errors in the calling configuration can be reported in the caller's context rather than inside the implementation details of the module. (#25054)New Kubernetes remote state storage backend: This backend stores state snapshots as Kubernetes secrets. (#19525)
BREAKING CHANGES:
As part of introducing a new heirarchical namespace for providers, Terraform now requires an explicit
source
specification for any provider that is not in the "hashicorp" namespace in the main public registry. (#24477)For more information, including information on the automatic upgrade process, refer to the v0.13 upgrade guide.
terraform import
: the previously-deprecated-provider
option is now removed. ([#24090](https://togithub.com/hashicorp/terrConfiguration
📅 Schedule: 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 these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.