blocks|key|723729|text|只要您在linux中，在终端中执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|723730|rm+-r+$(which+terraform)|code-block|syntax|javascript|723731|安装上一个版本：|723732|wget+https://releases.hashicorp.com/terraform/1.3.4/terraform_1.3.4_linux_amd64.zip+

unzip+terraform_1.3.4_linux_amd64.zip

mv+terraform+/usr/local/bin/terraform

terraform+--version|723733|就这样，我的朋友。|723734|编辑:我假设人们现在使用v1.3.5，所以以前的版本是v1.3.4。|723735|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

As long as you are in linux, do the following in the terminal:
<pre><code>rm -r $(which terraform)
</code></pre>
Install the previous version:
<pre><code>wget https://releases.hashicorp.com/terraform/1.3.4/terraform_1.3.4_linux_amd64.zip 

unzip terraform_1.3.4_linux_amd64.zip

mv terraform /usr/local/bin/terraform

terraform --version
</code></pre>
That's it, my friend.
EDIT: I've assumed people now use v1.3.5 so the previous version is v1.3.4.

blocks|key|589058|text|您还可以签出Terraform开关+--这将允许您轻松地在不同版本之间切换。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|589059|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/warrensbox/terraform-switcher^0|6|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You could also checkout <a href="https://github.com/warrensbox/terraform-switcher" rel="noreferrer">Terraform Switcher</a> - this will allow you to switch between different versions easily.

blocks|key|593911|text|首先，使用以下方法下载最新的包信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|593912|sudo+apt-get+update|offset|length|style|CODE|593913|降级的最简单方法是使用apt-get安装所需的版本--这将自动执行降级操作：|593914|显示可用版本的列表-+sudo+apt+list+-a+terraform|593915|terraform/xenial+0.13.5+amd64
terraform/xenial+0.13.4-2+amd64
...+etc|code-block|syntax|javascript|593916|或者使用sudo+apt+policy+terraform列出可用的版本|593917|安装所需的版本：|593918|sudo+apt-get+install+terraform=0.14.5|593919|或者，对于“干净”方法，在安装所需的版本之前删除现有版本：|593920|sudo+apt+remove+terraform|593921|entityMap^0|0|0|J|0|B|7|0|B|Q|0|0|4|P|0|0|0|11|0|0|0|P|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1C|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1G|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|11|$]]

First, download latest package information using:
<code>sudo apt-get update</code>
The simplest way to downgrade is to use <code>apt-get</code> to install the required version - this will automatically perform a downgrade:
Show a list of available versions - <code>sudo apt list -a terraform</code>
<pre><code>terraform/xenial 0.13.5 amd64
terraform/xenial 0.13.4-2 amd64
... etc
</code></pre>
or use <code>sudo apt policy terraform</code> to list available versions
Install the desired version:
<code>sudo apt-get install terraform=0.14.5</code>
Or, for a 'clean' approach, remove the existing version before installing the desired version:
<code>sudo apt remove terraform</code>

blocks|key|593882|text|这里还有其他有效的答案。如果像我一样，在从旧版本迁移到新版本时需要多个Terraform版本，这可能很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|593883|我用tfenv做这个：https://github.com/tfutils/tfenv|offset|length|593884|它提供了一个修改后的terraform脚本，它根据默认情况或目录或父目录中最接近的.+terraform版本文件查找正确的terraform可执行文件。这允许我们使用Terraform+0.12版本来处理迁移的内容，并将Terraform+0.11保留在遗留的内容中。|593885|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/tfutils/tfenv^0|0|B|W|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

There are other valid answers here. This may be useful if you have a situation, like I do, where you need multiple Terraform versions during a migration from an old version to a new version.

I use tfenv for that:
<a href="https://github.com/tfutils/tfenv" rel="nofollow noreferrer">https://github.com/tfutils/tfenv</a>

It provides a modified terraform script that does a lookup of the correct terraform executable based on a default or based on the closest .terraform-version file in the directory or parent directories. This allows us to use a version of Terraform 0.12 for our migrated stuff and keep Terraform 0.11 for our legacy stuff.

blocks|key|723775|text|你不应该再在ubuntu安装terraform了。一般说来，这个行业现在已经转向了码头。您可以像这样安装码头：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|723776|sudo+apt+install+-y+curl
curl+-LSs+get.docker.com+%7C+sh
sudo+groupadd+docker
sudo+usermod+-aG+docker+$USER|code-block|syntax|javascript|723777|安装之后，您可以像这样运行terraform：|723778|docker+run+-v+$PWD:/work+-w+/work+-v+~/.aws:/root/.aws+hashicorp/terraform:0.12.17+init|723779|假设您的.aws目录包含aws凭据。如果不是，您可以将挂载绑定(-v+~/.aws:/root/.aws)排除在命令之外，它将使用您选择使用的任何方案。您可以轻松地更改您正在使用的terraform版本，而无需安装任何东西。|offset|length|style|CODE|723780|与公认的答案相比，这种方法有很大的好处。首先是版本控制的易用性。如果您已经使用包管理器安装了terraform，您可以卸载它并安装所需的版本，或者您可以使用Linux替代版本(如果您的发行版支持它们，或者您使用的是Linux，或者是某种类型的包管理器--您可以使用Windows并下载并运行安装程序)。当然，这可能是一次性的事情，在这种情况下，你只做一次，你就会永远好，但在我的经验，这不是经常的情况，因为大多数团队需要更新版本由于安全控制，而那些不需要定期更新软件可能应该是。|723781|如果这不是一次性的事情，或者你不想玩太多的版本控制，那么你可以下载二进制文件，就像这篇文章上的评论指出的那样。很容易为每个版本提出一个目录方案，或者只需删除正在使用的目录，并将其完全替换。这可能非常适合您的用例。去适当的网站(我忘了哪一个--+Hashicorp还是GitHub回购的发布页面，你可以一直搜索它，尽管这也需要时间--这也是我的观点)，找到正确的版本并下载。|723782|或者，您只需键入docker+run+hashicorp/terraform:0.12.17，就可以自动从预先配置的在线可信回购中为您提取正确的版本。|723783|因此，安装新版本更容易，当然，docker将为您运行校验和，还将扫描图像以查找漏洞，并将结果报告给开发人员。当然，您可以自己完成所有这些操作，因为正如这个答案上的注释所述，它只是一个静态编译的二进制文件，所以没有麻烦只需安装就可以了。|723784|但还是没那么容易。另一个好处是，您可以轻松地将容器版本合并到坞-组合配置中，或者在K8S中运行它。同样，您可能不需要这种功能，但考虑到行业正朝着这个方向发展，您现在可以学习使用标准化的工具并在任何地方应用这些知识，或者您可以学习一种不同的技术来安装您现在使用的每一个工具(从GitHub版本中获取一些工具并复制二进制文件，其他您应该使用包管理器，其他您应该下载、解压缩和安装，还有一些应该通过安装程序从供应商网站上安装等等)。或者，你可以学习如何与码头，并应用同样的技巧，一切。大量的现代工具和软件现在都以这种“标准”的方式包装起来。这就是集装箱的真正意义--标准化。一个单一的方法或多或少适用于一切。|723785|因此，您得到了一种适用于大多数现代软件、额外安全性和更容易版本控制的标准化方法，无论您在哪个操作系统上运行(几乎--它确实覆盖了Linux、windows、osx、raspbian等)，它们的工作方式几乎完全相同。|723786|除了这里特别提到的安全方面还有其他好处，适用于企业环境，但我没有时间在这里详细介绍，但是如果您感兴趣，您可以看看Aqua和Prisma+Cloud+Compute之类的东西。当然，您还可以扩展基本的hashicorp/terraform容器，并添加您最喜欢的默认值。|723787|就我个人而言，我在工作中别无选择，只能运行windows+(没有wsl)，但我可以运行码头，因此我有一个带有别名的“瑞士军刀”容器，可以通过共享的码头套接字运行其他容器。这意味着在运行windows时，我将尽可能接近真实的Linux环境。我定期地释放我的工作容器，并且不希望每当我改变我正在使用的工具的版本时就重新构建它，所以我使用了一个别名来代替这些工具的最新版本，新的版本会自动地被拖到我的工作区中。如果这在我做的时候失败了，那么我可以在别名中指定一个版本并继续工作，直到我准备好升级为止。如果我在处理其他人的代码时需要降低工具的级别，我只需再次更改别名，旧版本就可以正常工作了。在我看来，这个工作流是我使用过的最简单的工作流程，我已经这样做了35年。|723788|我认为码头和这种工程方法比以前任何一种方法都更简单、更干净、更安全。我强烈建议大家都试一试。|723789|entityMap^0|0|0|0|0|W|K|0|0|0|8|12|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1E|8|@$M|1F|N|1G|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1J|8|@$M|1K|N|1L|O|P]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1N|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1O|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1P|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|1R|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|19|$]]

You shouldn't be installing terraform in ubuntu any more. Generally speaking, the industry has moved on to docker now. You can install docker like this:

<pre class="lang-sh prettyprint-override"><code>sudo apt install -y curl
curl -LSs get.docker.com | sh
sudo groupadd docker
sudo usermod -aG docker $USER
</code></pre>

Once installed you can run terraform like this:

<pre class="lang-sh prettyprint-override"><code>docker run -v $PWD:/work -w /work -v ~/.aws:/root/.aws hashicorp/terraform:0.12.17 init
</code></pre>

Assuming that your .aws directory contains your aws credentials. If not, you can leave that mount binding (<code>-v ~/.aws:/root/.aws</code>) out of the command and it'll work with whatever scheme you choose to use. You can change the version of terraform you are using with ease, without installing anything.

<hr>

There are significant benefits in this approach over the accepted answer. First is the ease of versioning. If you have installed terraform using a package manager you can either uninstall it and install the version you need, or you can play around with Linux alternatives (if your distro supports them, or you are using Linux, or a package manager of some sort -- you could be using Windows and have downloaded and run an installer). Of course, this might be a one-off thing, in which case you do it once and you're ok forever, but in my experience, that isn't often the case as most teams are required to update versions due to security controls, and those teams that aren't required to regularly update software probably should be. 

If this isn't a one-off thing, or you'd not like to play around too much with versioning then you could just download the binary, as one comment on this post points out. It's pretty easy to come up with a scheme of directories for each version, or just delete the one you're using and replace it completely. This may suit your use-case pretty well. Go to the appropriate website (I've forgotten which one -- Hashicorp or the GitHub repo's releases page, you can always search for it, though that takes time too -- which is my point) and find the right version and download it.

Or, you can just type <code>docker run hashicorp/terraform:0.12.17</code> and the right version will be automagically pulled for you from a preconfigured online trusted repo.

So, installing new versions is easier, and of course, docker will run the checksum for you, and will also have scanned the image for vulnerabilities and reported the results back to the developers. Of course, you can do all of this yourself, because as the comment on this answer states, it's just a statically compiled binary, so no hassle just install it and go.

Only it still isn't that easy. Another benefit would be the ease in which you could incorporate the containerised version into docker-compose configurations, or run it in K8S. Again, you may not need this capability, but given that the industry is moving that way, you can learn to do it using the standardised tools now and apply that knowledge everywhere, or you can learn a different technique to install every single tool you use now (get some from GitHub releases and copy the binary, others you should use the package manager, others you should download, unzip, and install, still others should be installed from the vendor website using an installer, etc. etc. etc.). Or, you can just learn how to do it with docker and apply the same trick to everything. The vast of modern tools and software are now packaged in this 'standard' manner. That's the point of containers really -- standardisation. A single approach more-or-less fits everything.

So, you get a standardised approach that fits most modern software, extra security, and easier versioning, and this all works almost exactly the same way no matter which operating system you're running on (almost -- it does cover Linux, windows, osx, raspbian, etc.). 

There are other benefits around security other than those specifically mentioned here, that apply in an enterprise environment, but I don't have time to go into a lot of detail here, but if you were interested you could look at things like Aqua and Prisma Cloud Compute. And of course you also have the possibility of extending the base hashicorp/terraform container and adding in your favourite defaults.

Personally, I have no choice in work but to run windows (without wsl), but I am allowed to run docker, so I have a 'swiss army knife' container with aliases to run other containers through the shared docker socket. This means that I get as close to a real Linux environment as possible while running windows. I dispose of my work container regularly, and wouldn't want to rebuild it whenever I change the version of a tool that I'm using, so I use an alias against the latest version of those tools, and new versions are automatically pulled into my workspace. If that breaks when I'm doing, then I can specify a version in the alias and continue working until I'm ready to upgrade. If I need to downgrade a tool when I'm working on somebody else's code I just change the alias again and everything works with the old version. It seems to me that this workflow is the easiest I've ever used, and I've been doing this for 35 years. 

I think that docker and this approach to engineering is simpler, cleaner, and more secure than any that has come before it. I strongly recommend that everyone try it.

I have installed a version (0.12.24) of Terraform which is later than the required version (0.12.17) specified in our configuration. How can I downgrade to that earlier version? My system is Linux Ubuntu 18.04.

How to downgrade Terraform to a previous version?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我已经安装了Terraform的版本(0.12.24)，它比我们配置中指定的所需版本(0.12.17)要晚。我怎样才能降级到那个早期版本呢？我的系统是LinuxUbuntu18.04。

问如何将Terraform降级为以前的版本？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将Terraform降级为以前的版本？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何将Terraform降级为以前的版本？
EN