Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package terraform for openSUSE:Factory checked in at 2021-10-16 22:47:23 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/terraform (Old) and /work/SRC/openSUSE:Factory/.terraform.new.1890 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "terraform" Sat Oct 16 22:47:23 2021 rev:25 rq:925600 version:1.0.2 Changes: -------- --- /work/SRC/openSUSE:Factory/terraform/terraform.changes 2021-04-17 23:25:19.269630458 +0200 +++ /work/SRC/openSUSE:Factory/.terraform.new.1890/terraform.changes 2021-10-16 22:47:59.408709610 +0200 @@ -1,0 +2,357 @@ +Thu Jul 8 08:21:11 UTC 2021 - John Paul Adrian Glaubitz <adrian.glaub...@suse.com> + +- Update to 1.0.2 + BUG FIXES: + * `terraform show`: Fix crash when rendering JSON plan with sensitive values in state (#29049) + * config: The `floor` and `ceil` functions no longer lower the precision of arguments to what + would fit inside a 64-bit float, instead preserving precision in a similar way as most other + arithmetic functions. (#29110) + * config: The `flatten` function was incorrectly treating null values of an unknown type as if + they were unknown values. Now it will treat them the same as any other non-list/non-tuple value, + flattening them down into the result as-is. (#29110) +- from version 1.0.1 + ENHANCEMENTS: + * `terraform show`: The JSON plan output now indicates which state values are sensitive. (#28889) + * cli: The macOS builds will now resolve hostnames using the system's DNS resolver, rather than the + Go library's (incomplete) emulation of it. In particular, this will allow for the more complex + resolver configurations often created by VPN clients on macOS, such as when a particular domain + must be resolved using different nameservers while VPN connection is active. + BUG FIXES: + * `terraform show`: Fix crash with deposed instances in json plan output. (#28922) + * `terraform show`: Fix an issue where the JSON configuration representation was missing + fully-unwrapped references. (#28884) + * `terraform show`: Fix JSON plan resource drift to remove unchanged resources. (#28975) + * core: Fix crash when provider modifies and unknown block during plan. (#28941) + * core: Diagnostic context was missing for some errors when validating blocks. (#28979) + * core: Fix crash when calling `setproduct` with unknown values. (#28984) + * backend/remote: Fix faulty Terraform Cloud version check when migrating state to the remote backend + with multiple local workspaces. (#28864) +- from version 1.0.0 + Terraform v1.0 is an unusual release in that its primary focus is on stability, and it represents the + culmination of several years of work in previous major releases to make sure that the Terraform language + and internal architecture will be a suitable foundation for forthcoming additions that will remain + backward compatible. + + Terraform v1.0.0 intentionally has no significant changes compared to Terraform v0.15.5. You can consider + the v1.0 series as a direct continuation of the v0.15 series; we do not intend to issue any further releases + in the v0.15 series, because all of the v1.0 releases will be only minor updates to address bugs. + + For all future minor releases with major version 1, we intend to preserve backward compatibility as described + in detail in [the Terraform v1.0 Compatibility Promises](https://www.terraform.io/docs/language/v1-compatibility- + promises.html). The later Terraform v1.1.0 will, therefore, be the first minor release with new features that + we will implement with consideration of those promises. +- from version 0.15.5 + BUG FIXES: + * `terraform plan` and `terraform apply`: Don't show "Objects have changed" notification + when the detected changes are only internal details related to legacy SDK quirks. (#28796) + * core: Prevent crash during planning when encountering a deposed instance that has been + removed from the configuration. (#28766) + * core: Fix crash when rendering changes to deposed instances outside of Terraform. (#28796) + * core: Restore a missing error when attempting to import a non-existent remote object. (#28808) + * core: Fix bug where Terraform failed to release the state lock when applying a stale + saved plan failed. (#28819) +- from version 0.15.4 + NEW FEATURES: + * **Noting changes made outside of Terraform:** Terraform has always, by default, made a point + during the planning operation of reading the current state of remote objects in order to detect + any changes made outside of Terraform, to make sure the plan will take those into account. + + Terraform will now report those detected changes as part of the plan result, in order to give + additional context about the planned changes. We've often heard that people find it confusing + when a plan includes a change that doesn't seem to be prompted by any recent change in the + _configuration_, and so this feature is aiming to provide the previously-missing explanation + for situations where Terraform is planning to undo a change. + + It can also be useful just as general information when the change _won't_ be undone by Terraform: + if you've intentionally made a change outside of Terraform and mirrored that change in your + configuration then Terraform will now confirm that it noticed the change you made and took it + into account when planning. + + By default this new output is for information only and doesn't change any behavior. If Terraform + detects a change you were _expecting_ then you don't need to take any additional action to respond + to it. However, we've also added a new planning mode `-refresh-only` which allows you to explicitly + plan and apply the action of writing those detected changes to the Terraform state, which serves + as a plannable replacement for `terraform refresh`. We don't have any plans to remove the long-standing + `terraform refresh` command, but we do recommend using `terraform apply -refresh-only` instead in most + cases, because it will provide an opportunity to review what Terraform detected before updating the + Terraform state. + UPGRADE NOTES: + * This release adds some new reserved reference prefixes to make them available for later work. These + are `resource.`, `template.`, `arg.`, and `lazy.`. We don't expect these additions to cause problems + for most existing configurations, but could cause a conflict if you are using a custom provider which + has a resource type named exactly "resource", "template", "arg", or "lazy". In that unlikely event, + you can escape references to resources of those types by adding a `resource.` prefix; for example, + if you have a `resource "template" "foo"` then you can change references to it from `template.foo` + to `resource.template.foo` in order to escape the new meaning. + ENHANCEMENTS: + * config: The various functions that compute hashs of files on disk, like `filesha256`, will now stream + the contents of the given file into the hash function in smaller chunks. Previously they would always + read the entire file into memory before hashing it, due to following a similar implementation strategy + as the `file` function. (#28681) + * config: Some new escaping syntax which is not yet useful but will be part of the backward-compatibility + story for certain future language editions. (#28709) + * core: Resource diagnostics are no longer lost on remote state storage failures (#28724) + * core: Diagnostics from provisioner failures are now shown in CLI output (#28753) + * `terraform init`: add a new `-migrate-state` flag instead of automatic state migration, to prevent failing + when old backend config is not usable (#28718) + * `terraform plan` and `terraform apply`: will now report any changes Terraform detects during the "refresh" + phase for each managed object, providing confirmation that Terraform has seen those changes and, where + appropriate, extra context to help understand the planned change actions that follow. (#28634) + * `terraform plan` and `terraform apply`: now have a new option `-refresh-only` to activate the "refresh only" + planning mode, which causes Terraform to ignore any changes suggested by the configuration but still detect + any changes made outside of Terraform since the latest `terraform apply`. (#28634) + * backend/gcs: Terraform Core now supports Workload Identity Federation. The federated JSON credentials must be + loaded through the `GOOGLE_APPLICATION_CREDENTIALS` environment variable. This is also available in the Google + Provider in versions newer than v3.61. (#28296) + * backend/remote: supports several new CLI options when running plans and applies with Terraform Cloud: + `-refresh=false`, `-replace`, and `-refresh-only`. (#28746) + BUG FIXES: + * core: Fix sensitivity handling with plan values, which could cause the sensitive marks to be lost during apply + leading to a perpetual diff (#28687) + * core: Fix crash when specifying SSH `bastion_port` in a resource `connection` block (#28665) + * core: Terraform will now upgrade and refresh (unless disabled) deposed objects during planning, in a similar + manner as for objects that have been removed from the configuration. "Deposed" is how Terraform represents + the situation where a `create_before_destroy` replacement failed to destroy the old object, in which case + Terraform needs to track both the new and old objects until the old object is successfully deleted. Refreshing + these during planning means that you can, if you wish, delete a "deposed" object manually outside of Terraform + and then have Terraform detect that you've done so. (#28634) + * config: Improve the sensitivity support for `lookup` and `length` functions, which were accidentally omitted + from the larger update in 0.15.1 (#28509) + * backend/gcs: Fixed a bug where service account impersonation didn't work if the original identity was another + service account (#28139) +- from version 0.15.3 + ENHANCEMENTS: + * `terraform show`: Add data to the JSON plan output describing which changes caused a resource to be replaced + (#28608) + BUG FIXES: + * `terraform show`: Fix crash for JSON plan output of new resources with sensitive attributes in nested blocks + (#28624) +- from version 0.15.2 + ENHANCEMENTS: + * `terraform plan` and `terraform apply`: Both now support a new planning option `-replace=...` which takes the + address of a resource instance already tracked in the state and forces Terraform to upgrade either an update or + no-op plan for that instance into a "replace" (either destroy-then-create or create-then-destroy depending on + configuration), to allow replacing a degraded object with a new object of the same configuration in a single + action and preview the effect of that before applying it. + * `terraform apply`: Now has a `-destroy` option for symmetry with `terraform plan -destroy`, which makes `terraform + destroy` effectively an alias for `terraform apply -destroy`. This change is only for consistency between `terraform + plan` and `terraform apply`; there are no current plans to deprecate `terraform destroy`. (#28489) + * core: Update HCL to allow better planning of dynamic blocks (#28424) + * core: Unmark values when planning data sources (#28539) + BUG FIXES: + * command/format: Fix various issues with nested-type attribute formatting (#28600) + * core: Fix JSON plan output to add sensitivity data for provider-specified sensitive attribute values (#28523) + * cli: Fix missing "forces replacement" UI for attribute changes which are marked as sensitive by the provider (#28583) + * cli: Fix crash when rendering diagnostic caused by missing trailing quote (#28598) + * config: Fix crash when calling `setproduct` with one or more empty collections (#28607) +- from version 0.15.1 + ENHANCEMENTS: + * config: Various Terraform language functions now have more precise inference rules for propagating the "sensitive" + characteristic values. + + The affected functions are `chunklist`, `concat`, `flatten`, `keys`, `length`, `lookup`, `merge`, `setproduct`, + `tolist`, `tomap`, `values`, and `zipmap`. The details are a little different for each of these but the general + idea is to, as far as possible, preserve the sensitive characteristic on individual element or attribute values + in result structures rather than always conservatively applying sensitivity to the whole result. + + The primary benefit of these improvements is that you can now use these functions as part of constructing maps for + `for_each` in situations where the input collection is never sensitive but some of the elements/attributes inside + might be. (#28446) + * cli: Update the HashiCorp public key (#28505) + * cli: Diagnostic messages can now be annotated with resource and provider addresses. (#28275) + * cli: `terraform login` now has a new user experience for successful log-ins to Terraform Cloud and Terraform + Enterprise. (#28487) + * core: Minor graph performance optimizations. (#28329) + BUG FIXES: + * config: Fix validation error when passing providers from a non-default namespace into modules. (#28414) + * cli: Fix missing colors and extraneous resource summary for plan/apply with the remote backend. (#28409) + * cli: Diagnostics messages will only indicate that a referenced value is sensitive if that value is _directly_ + sensitive, as opposed to being a complex-typed value that _contains_ a sensitive value. (#28442) + * core: Don't trigger data source reads from changes in sibling module instances. (#28267) + * core: Restore saved dependencies when a resource destroy operation fails. (#28317) + * core: Fix crash when setting sensitive attributes to a sensitive value. (#28383) + * core: Loosen output value sensitivity requirement for non-root modules. This means that modules which may + receive sensitive values as input variables no longer need to mark all related outputs as sensitive. The + requirement for root modules to specify the `sensitive` attribute for sensitive values remains, with an + extended diagnostic message to explain why. (#28472) + * provisioner: Fix panic with unexpected null values in provisioner configuration (#28457) +- from version 0.15.0 + 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](https://www.terraform.io/upgrade-guides/0-15.html) + 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 explicit `configuration_aliases` argument within the `required_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 empty `provider` block. (#27739) + + * The `list` and `map` functions, both of which were deprecated since Terraform v0.12, are now removed. You can + replace uses of these functions with `tolist([...])` and `tomap({...})` 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] + (https://docs.microsoft.com/en-us/windows/console/classic-vs-vt). Terraform previously required these terminal + features on all other platforms, and now requires them on Windows too. + ++++ 160 more lines (skipped) ++++ between /work/SRC/openSUSE:Factory/terraform/terraform.changes ++++ and /work/SRC/openSUSE:Factory/.terraform.new.1890/terraform.changes Old: ---- terraform-0.14.10.obscpio terraform-0.14.10.tar.xz vendor.tar.xz New: ---- terraform-1.0.2.obscpio terraform-1.0.2.tar.gz vendor.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ terraform.spec ++++++ --- /var/tmp/diff_new_pack.yTNW1R/_old 2021-10-16 22:48:00.120710210 +0200 +++ /var/tmp/diff_new_pack.yTNW1R/_new 2021-10-16 22:48:00.124710213 +0200 @@ -17,17 +17,16 @@ Name: terraform -Version: 0.14.10 +Version: 1.0.2 Release: 0 Summary: Tool for building infrastructure safely and efficiently License: MPL-2.0 Group: System/Management URL: https://www.terraform.io/ -Source: %{name}-%{version}.tar.xz -Source1: vendor.tar.xz +Source: %{name}-%{version}.tar.gz +Source1: vendor.tar.gz Source99: terraform-rpmlintrc BuildRequires: golang-packaging -BuildRequires: xz BuildRequires: golang(API) >= 1.15 # See: https://github.com/hashicorp/terraform/issues/22807 ExcludeArch: %{ix86} ++++++ _service ++++++ --- /var/tmp/diff_new_pack.yTNW1R/_old 2021-10-16 22:48:00.156710241 +0200 +++ /var/tmp/diff_new_pack.yTNW1R/_new 2021-10-16 22:48:00.156710241 +0200 @@ -3,16 +3,19 @@ <param name="url">https://github.com/hashicorp/terraform</param> <param name="scm">git</param> <param name="filename">terraform</param> - <param name="versionformat">0.14.10</param> - <param name="revision">v0.14.10</param> + <param name="versionformat">1.0.2</param> + <param name="revision">v1.0.2</param> <param name="exclude">.git</param> </service> <service name="tar" mode="disabled"/> <service name="recompress" mode="disabled"> <param name="file">*.tar</param> - <param name="compression">xz</param> + <param name="compression">gz</param> </service> <service name="set_version" mode="disabled"> <param name="basename">terraform</param> </service> + <service name="go_modules" mode="disabled"> + <param name="archive">terraform-1.0.2.tar.gz</param> + </service> </services> ++++++ terraform-0.14.10.obscpio -> terraform-1.0.2.obscpio ++++++ /work/SRC/openSUSE:Factory/terraform/terraform-0.14.10.obscpio /work/SRC/openSUSE:Factory/.terraform.new.1890/terraform-1.0.2.obscpio differ: char 28, line 1 ++++++ terraform.obsinfo ++++++ --- /var/tmp/diff_new_pack.yTNW1R/_old 2021-10-16 22:48:00.200710277 +0200 +++ /var/tmp/diff_new_pack.yTNW1R/_new 2021-10-16 22:48:00.200710277 +0200 @@ -1,5 +1,5 @@ name: terraform -version: 0.14.10 -mtime: 1617818809 -commit: a357f1bf83141701c5e7d689d4657172efd233f1 +version: 1.0.2 +mtime: 1625679683 +commit: e33a4c51daff2fc81734f192bc458b03ec1c9ca8
