Skip to content

Releases: liquidweb/terraform-provider-liquidweb

v1.7.1

11 Oct 19:12
646294b
Compare
Choose a tag to compare

Fixed a panic in the load balancer resource, but mostly added new examples for some deployments.

v1.7.0

19 Sep 18:37
33f90ad
Compare
Choose a tag to compare

Initial release to hit registry.terraform.io

1.5.8

17 Sep 00:44
Compare
Choose a tag to compare

Changelog

8c335b3 Upgrade to go 1.13

1.5.4

16 Sep 23:31
Compare
Choose a tag to compare
Fix reference

1.5.3

16 Sep 23:22
Compare
Choose a tag to compare
goreleaser

1.5.2

16 Sep 22:54
Compare
Choose a tag to compare
Releases

1.5.0

15 Aug 16:02
Compare
Choose a tag to compare

Project-wide

  • Change the development workflow so it can be done entirely within a container, no more host setup.
make shell
$ terraform version
  • Added tests for existing helpers (helpers.go).
  • Terraform 0.12.x syntax updates across the board.

Tracing

Tracing via Jaeger is available so various actions: successful API patterns, bottlenecks and problems can be identified recognized accordingly. It's important to capture where we're getting things right as much as wrong.

make jaeger
xdg-open http://localhost:16686/search

In the development container:

JAEGER_DISABLED=false EXAMPLE=./examples/storm_servers make apply

Tracing is enabled if JAEGER_DISABLED is set to false and by default is disabled. This requires the jaeger container to be running and general use with an external Terraform project isn't yet supported.

Storm Servers

  • Update resource to use Liquid Web Golang API client library and eliminate lots of boilerplate.
  • Update implementation to use idiomatic Golang error handling (possible due to the refactor of liquidweb-go).
  • Fix destroy so that it waits for the server to be truly destroyed.
  • Fix for computed & optional properties which were previously just computed causing unnecessary changes to plan/apply.
  • More intelligent updating of resource data based on the given operation -- no excess API reads & resource updates.
  • Handle three undocumented cases where status could be returned incorrectly or not at all.
  • Handle backup and bandwidth parameters so they're typed appropriately and reflect.

Load Balancers

Changed the load balancer API:

resource "liquidweb_network_load_balancer" "testing_some_space_balls" {
...
  services = [
    {
      src_port  = 80
      dest_port = 80
    },
    {
      src_port  = 1337
      dest_port = 1337
    },
  ]

is now

resource "liquidweb_network_load_balancer" "testing_some_space_balls" {
...
  service {
    src_port  = 80
    dest_port = 80
  }

  service {
    src_port  = 1337
    dest_port = 1337
  }