Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package terraform for openSUSE:Factory
checked in at 2022-09-27 20:14:22
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/terraform (Old)
and /work/SRC/openSUSE:Factory/.terraform.new.2275 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "terraform"
Tue Sep 27 20:14:22 2022 rev:40 rq:1006381 version:1.3.0
Changes:
--------
--- /work/SRC/openSUSE:Factory/terraform/terraform.changes 2022-09-12
19:08:41.786611921 +0200
+++ /work/SRC/openSUSE:Factory/.terraform.new.2275/terraform.changes
2022-09-27 20:14:35.817914707 +0200
@@ -1,0 +2,47 @@
+Sun Sep 25 07:06:14 UTC 2022 - Johannes Kastl <ka...@b1-systems.de>
+
+- update to 1.3.0:
+ * NEW FEATURES:
+ - Optional attributes for object type constraints: When declaring an input
variable whose type constraint includes an object type, you can now declare
individual attributes as optional, and specify a default value to use if the
caller doesn't set it. For example:
+ - Added functions: startswith and endswith allow you to check whether a
given string has a specified prefix or suffix. (#31220)
+ * UPGRADE NOTES:
+ - terraform show -json: Output changes now include more detail about the
unknown-ness of the planned value. Previously, a planned output would be marked
as either fully known or partially unknown, with the after_unknown field having
value false or true respectively. Now outputs correctly expose the full
structure of unknownness for complex values, allowing consumers of the JSON
output format to determine which values in a collection are known only after
apply.
+ - terraform import: The -allow-missing-config has been removed, and at
least an empty configuration block must exist to import a resource.
+ - Consumers of the JSON output format expecting on the after_unknown field
to be only false or true should be updated to support the change representation
described in the documentation, and as was already used for resource changes.
(#31235)
+ - AzureRM Backend: This release concludes the deprecation cycle started in
Terraform v1.1 for the azurerm backend's support of "ADAL" authentication. This
backend now supports only "MSAL" (Microsoft Graph) authentication.
+ - This follows from Microsoft's own deprecation of Azure AD Graph, and so
you must follow the migration instructions presented in that Azure
documentation to adopt Microsoft Graph and then change your backend
configuration to use MSAL authentication before upgrading to Terraform v1.3.
+ - When making requests to HTTPS servers, Terraform will now reject invalid
handshakes that have duplicate extensions, as required by RFC 5246 section
7.4.1.4 and RFC 8446 section 4.2. This may cause new errors when interacting
with existing buggy or misconfigured TLS servers, but should not affect correct
servers.
+ - This only applies to requests made directly by Terraform CLI, such as
provider installation and remote state storage. Terraform providers are
separate programs which decide their own policy for handling of TLS handshakes.
+ - The following backends, which were deprecated in v1.2.3, have now been
removed: artifactory, etcd, etcdv3, manta, swift. The legacy backend name azure
has also been removed, because the current Azure backend is named azurerm.
(#31711)
+ * ENHANCEMENTS:
+ - config: Optional attributes for object type constraints, as described
under new features above. (#31154)
+ - config: New built-in function timecmp allows determining the ordering
relationship between two timestamps while taking potentially-different UTC
offsets into account. (#31687)
+ - config: When reporting an error message related to a function call,
Terraform will now include contextual information about the signature of the
function that was being called, as an aid to understanding why the call might
have failed. (#31299)
+ - config: When reporting an error or warning message that isn't caused by
values being unknown or marked as sensitive, Terraform will no longer mention
any values having those characteristics in the contextual information presented
alongside the error. Terraform will still return this information for the small
subset of error messages that are specifically about unknown values or
sensitive values being invalid in certain contexts. (#31299)
+ - config: moved blocks can now describe resources moving to and from
modules in separate module packages. (#31556)
+ - terraform fmt now accepts multiple target paths, allowing formatting of
several individual files at once. (#31687)
+ - terraform init: provider installation errors now mention which host
Terraform was downloading from (#31524)
+ - CLI: Terraform will report more explicitly when it is proposing to
delete an object due to it having moved to a resource instance that is not
currently declared in the configuration. (#31695)
+ - CLI: When showing the progress of a remote operation running in
Terraform Cloud, Terraform CLI will include information about pre-plan run
tasks (#31617)
+ - The AzureRM Backend now only supports MSAL (and Microsoft Graph) and no
longer makes use of ADAL (and Azure Active Directory Graph) for authentication
(#31070)
+ - The COS backend now supports global acceleration. (#31425)
+ - provider plugin protocol: The Terraform CLI now calls PlanResourceChange
for compatible providers when destroying resource instances. (#31179)
+ - As an implementation detail of the Terraform Cloud integration,
Terraform CLI will now capture and upload the JSON integration format for state
along with any newly-recorded state snapshots, which then in turn allows
Terraform Cloud to provide that information to API-based external integrations.
(#31698)
+ * BUG FIXES:
+ - config: Terraform was not previously evaluating preconditions and
postconditions during the apply phase for resource instances that didn't have
any changes pending, which was incorrect because the outcome of a condition can
potentially be affected by changes to other objects in the configuration.
Terraform will now always check the conditions for every resource instance
included in a plan during the apply phase, even for resource instances that
have "no-op" changes. This means that some failures that would previously have
been detected only by a subsequent run will now be detected during the same run
that caused them, thereby giving the feedback at the appropriate time. (#31491)
+ - terraform show -json: Fixed missing markers for unknown values in the
encoding of partially unknown tuples and sets. (#31236)
+ - terraform output CLI help documentation is now more consistent with
web-based documentation. (#29354)
+ - terraform init: Error messages now handle the situation where the
underlying HTTP client library does not indicate a hostname for a failed
request. (#31542)
+ - terraform init: Don't panic if a child module contains a resource with a
syntactically-invalid resource type name. (#31573)
+ - CLI: The representation of destroying already-null output values in a
destroy plan will no longer report them as being deleted, which avoids
reporting the deletion of an output value that was already absent. (#31471)
+ - terraform import: Better handling of resources or modules that use
for_each, and situations where data resources are needed to complete the
operation. (#31283)
+ * EXPERIMENTS:
+ - This release concludes the module_variable_optional_attrs experiment,
which started in Terraform v0.14.0. The final design of the optional attributes
feature is similar to the experimental form in the previous releases, but with
two major differences:
+ - The optional function-like modifier for declaring an optional attribute
now accepts an optional second argument for specifying a default value to use
when the attribute isn't set by the caller. If not specified, the default value
is a null value of the appropriate type as before.
+ - The built-in defaults function, previously used to meet the use-case of
replacing null values with default values, will not graduate to stable and has
been removed. Use the second argument of optional inline in your type
constraint to declare default values instead.
+ - If you have any experimental modules that were participating in this
experiment, you will need to remove the experiment opt-in and adopt the new
syntax for declaring default values in order to migrate your existing module to
the stablized version of this feature. If you are writing a shared module for
others to use, we recommend declaring that your module requires Terraform
v1.3.0 or later to give specific feedback when using the new feature on older
Terraform versions, in place of the previous declaration to use the
experimental form of this feature:
+ terraform {
+ required_version = ">= 1.3.0"
+ }
+
+-------------------------------------------------------------------
Old:
----
terraform-1.2.9.obscpio
terraform-1.2.9.tar.gz
New:
----
terraform-1.3.0.obscpio
terraform-1.3.0.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ terraform.spec ++++++
--- /var/tmp/diff_new_pack.Etf3Zq/_old 2022-09-27 20:14:37.229917782 +0200
+++ /var/tmp/diff_new_pack.Etf3Zq/_new 2022-09-27 20:14:37.233917791 +0200
@@ -17,7 +17,7 @@
Name: terraform
-Version: 1.2.9
+Version: 1.3.0
Release: 0
Summary: Tool for building infrastructure safely and efficiently
License: MPL-2.0
++++++ _service ++++++
--- /var/tmp/diff_new_pack.Etf3Zq/_old 2022-09-27 20:14:37.273917878 +0200
+++ /var/tmp/diff_new_pack.Etf3Zq/_new 2022-09-27 20:14:37.273917878 +0200
@@ -3,8 +3,8 @@
<param name="url">https://github.com/hashicorp/terraform</param>
<param name="scm">git</param>
<param name="filename">terraform</param>
- <param name="versionformat">1.2.9</param>
- <param name="revision">v1.2.9</param>
+ <param name="versionformat">1.3.0</param>
+ <param name="revision">v1.3.0</param>
<param name="exclude">.git</param>
</service>
<service name="tar" mode="disabled"/>
@@ -16,7 +16,7 @@
<param name="basename">terraform</param>
</service>
<service name="go_modules" mode="disabled">
- <param name="archive">terraform-1.2.9.tar.gz</param>
+ <param name="archive">terraform-1.3.0.tar.gz</param>
</service>
</services>
++++++ terraform-1.2.9.obscpio -> terraform-1.3.0.obscpio ++++++
/work/SRC/openSUSE:Factory/terraform/terraform-1.2.9.obscpio
/work/SRC/openSUSE:Factory/.terraform.new.2275/terraform-1.3.0.obscpio differ:
char 49, line 1
++++++ terraform-1.2.9.tar.gz -> terraform-1.3.0.tar.gz ++++++
++++ 37769 lines of diff (skipped)
++++++ terraform.obsinfo ++++++
--- /var/tmp/diff_new_pack.Etf3Zq/_old 2022-09-27 20:14:38.429920396 +0200
+++ /var/tmp/diff_new_pack.Etf3Zq/_new 2022-09-27 20:14:38.429920396 +0200
@@ -1,5 +1,5 @@
name: terraform
-version: 1.2.9
-mtime: 1662583736
-commit: 2bed243125baeb861970dc9bb2e5f4713d8e3669
+version: 1.3.0
+mtime: 1663767632
+commit: 5c239ecd6ac3a183bb4852940f2f2d1af1a766ce
++++++ vendor.tar.gz ++++++
/work/SRC/openSUSE:Factory/terraform/vendor.tar.gz
/work/SRC/openSUSE:Factory/.terraform.new.2275/vendor.tar.gz differ: char 5,
line 1
