-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terraform 0.12.0-alpha2 #50781
Terraform 0.12.0-alpha2 #50781
Conversation
Success on x86_64-darwin (full log) Attempted: terraform, terraform_0_12 Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: terraform, terraform_0_12 Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: terraform, terraform_0_12 Partial log (click to expand)
|
@@ -22593,11 +22593,12 @@ with pkgs; | |||
terraform_0_10-full | |||
terraform_0_11 | |||
terraform_0_11-full | |||
terraform_0_12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding new versions is fine, but what about removing old ones?
I don't see terraform maintaining previous releases so we should also limit the amounts of versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. Since 0.12 is actually functionally different we'll probably want to keep 0.11 around for a while after the fact, but the earlier ones are probably disposable. I do remember @shlevy having some use case for even earlier versions but I don't know if he still does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed, deleted a bunch of old versions with associated dependants
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually even 0.10 should be safe to delete, there hasn't been any backward-incompatible changes in 0.11
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed from my standpoint, I'd just make sure that @shlevy doesn't have some weird corner case because I do recall him saying he had a reason to keep the older one around.
The rest of the PR seems fine to me, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK to delete some of the old ones. We ran into cases where TF was updating quickly and breaking backwards compat but certainly the oldest ones can be removed now. We're using 0.11 currently IIRC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, deleting 0.10 as well
These are very old and blocking cleaning old terraform releases
e5ecec3
to
098c192
Compare
Success on x86_64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: terraform, terraform_0_12 The following builds were skipped because they don't evaluate on x86_64-darwin: terragrunt Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
098c192
to
6529d91
Compare
Success on x86_64-darwin (full log) Attempted: terraform, terraform_0_12 The following builds were skipped because they don't evaluate on x86_64-darwin: terragrunt Partial log (click to expand)
|
providers are already compiled independently so we don't need Hydra to follow terraform_MAJ_MIN_full to have them all compiled. Instead of having to create two aliases per release, add a "full" passthru for that common use-case. Eg: terraform_0_11_full -> terraform_0_11.full
Success on x86_64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
6529d91
to
85e9542
Compare
Success on x86_64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: terraform, terraform_0_12 The following builds were skipped because they don't evaluate on x86_64-darwin: terragrunt Partial log (click to expand)
|
85e9542
to
e28d314
Compare
Failure on aarch64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: terraform, terraform_0_12 The following builds were skipped because they don't evaluate on x86_64-darwin: terragrunt Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: terraform, terraform_0_12, terragrunt Partial log (click to expand)
|
Thanks for doing this! |
Is it intentional that |
Is it intentional that `nix-env -u` switches me from terraform 0.11 to this pre-release package?
That's how Nix version comparison works, but that's probably not
intentional. I believe, the pre-release package should have been given a
distinct name (e.g., `terraform-unstable`).
|
Motivation for this change
test terraform 0.12 before it's released
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)