Can we get a new release 0.1.3?

[nodesocket]

Terraform v0.10.1 was just released. Hoping to get some patches and fixes (#292) pushed.

[danawillow]

Just released! We were planning on one for this week anyway :)

[nodesocket]

Thanks @danawillow

[nodesocket]

@danawillow did this update? It is not clear.

iMac ➜  terraform git:(master) terraform init
Downloading modules...
Get: file:///Users/justin/Sites/my-project-here/terraform/modules/node

Initializing the backend...

Initializing provider plugins...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.google: version = "~> 0.1"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

[danawillow]

I don't work on core so I don't have a good sense of the messages- feel free to file an issue there that it should say what got downloaded. In the meantime, I would just try adding something that's new in the new version and seeing if terraform plan complains :)

[apparentlymart]

Hi @nodesocket!

If you already had a version of the provider installed, terraform init won't upgrade it unless you specifically run terraform init -upgrade to indicate that you want to potentially replace your existing version. init is conservative by default because init is used for a number of different purposes, such as switching backends or installing modules, and we thought it would be suprising/annoying if it were impossible to do those actions without implicitly upgrading installed providers.

[nodesocket]

@apparentlymart yah I just noticed in fact, I did not upgrade providers after all:

MacBook-Pro ➜  darwin_amd64 git:(master) ✗ ll
total 65232
-rwxr-xr-x@ 1 justin  staff    82B Aug 17 16:29 lock.json
-rwxr-xr-x@ 1 justin  staff    32M Aug  3 16:43 terraform-provider-google_v0.1.2_x4

Running terraform init -upgrade worked though. Perhaps adding each plugin/provider and version to terraform version would be helpful.

MacBook-Pro ➜  terraform git:(master) ✗ terraform version
Terraform v0.10.2
  - google v0.1.2

Just created a PR to the README.md that adds a one-liner instructions for others wondering how to upgrade. #338

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!