diff --git a/website/docs/cli/install/_category_.json b/website/docs/cli/install/_category_.json deleted file mode 100644 index f0ff25be76..0000000000 --- a/website/docs/cli/install/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Install" -} diff --git a/website/docs/cli/install/apt.mdx b/website/docs/cli/install/apt.mdx deleted file mode 100644 index 6a2cba83bb..0000000000 --- a/website/docs/cli/install/apt.mdx +++ /dev/null @@ -1,70 +0,0 @@ ---- -description: >- - The OpenTofu APT repositories contain distribution-specific OpenTofu - packages for both Debian and Ubuntu systems. ---- - -# APT Packages for Debian and Ubuntu - -:::danger Warning -The instructions below are out of date and will be updated as OpenTofu starts distributing Linux packages. Please follow the [relevant issue](https://github.com/opentofu/opentofu/issues/567) in the OpenTofu repository. - -In the meantime, see currently available installation instructions [here](/docs/intro/install). -::: - -The primary distribution packages for OpenTofu are `.zip` archives containing -single executable files that you can extract anywhere on your system. However, -for easier integration with configuration management tools and other systematic -system configuration strategies, we also offer package repositories for -Debian and Ubuntu systems, which allow you to install OpenTofu using the -`apt install` command or any other APT frontend. - -If you are instead using Red Hat Enterprise Linux, CentOS, or Fedora, you -might prefer to [install OpenTofu from our Yum repositories](/docs/cli/install/yum). - -## Repository Configuration - -Please follow the instructions in the [Official Packaging Guide](https://www.placeholderplaceholderplaceholder.com/official-packaging-guide). - -## Supported Architectures - -The OpenTofu APT server has packages only for the `amd64` -architecture, which is also sometimes known as `x86_64`. - -There are no official packages available for other architectures, such as -`arm64`. If you wish to use OpenTofu on a non-`amd64` system, -[download a normal release `.zip` file](/docs/downloads) instead. - -## Installing a Specific Version of OpenTofu - -The OpenTofu APT repositories contain multiple versions of OpenTofu, but -because the packages are all named `tofu` it is impossible to install -more than one version at a time, and `apt install` will default to selecting -the latest version. - -It's often necessary to match your OpenTofu version with what a particular -configuration is currently expecting. You can use the following command to -see which versions are currently available in the repository index: - -```bash -apt policy tofu -``` - -If your workflow requires using multiple versions of OpenTofu at the same -time, for example when working through a gradual upgrade where not all -of your configurations are upgraded yet, we recommend that you use the -official release `.zip` files instead of the APT packages, so you can install -multiple versions at once and then select which to use for each command you -run. - -All published packages include a revision number by -default, starting with `-1`. This change means that in the case that we need -to publish an updated package for any reason, installers can automatically -retrieve the latest revision. - -You can install the latest revision for a particular version by including the -version in the `apt install` command, as follows: - -```bash -sudo apt install tofu=1.4.4-* -``` diff --git a/website/docs/cli/install/yum.mdx b/website/docs/cli/install/yum.mdx deleted file mode 100644 index f7f0c9da97..0000000000 --- a/website/docs/cli/install/yum.mdx +++ /dev/null @@ -1,120 +0,0 @@ ---- -title: Yum Packages for Red Hat Enterprise Linux, Fedora, and Amazon Linux -description: >- - The OpenTofu Yum repositories contain distribution-specific OpenTofu - packages for Red Hat Enterprise Linux, Fedora, and Amazon Linux systems. ---- - -# Yum/DNF Packages for RHEL, CentOS, and Fedora - -:::danger Warning -The instructions below are out of date and will be updated as OpenTofu starts distributing Linux packages. Please follow the [relevant issue](https://github.com/opentofu/opentofu/issues/567) in the OpenTofu repository. - -In the meantime, see currently available installation instructions [here](/docs/intro/install). -::: - -The primary distribution packages for OpenTofu are `.zip` archives containing -single executable files that you can extract anywhere on your system. However, -for easier integration with configuration management tools and other systematic -system configuration strategies, we also offer package repositories for -RedHat Enterprise Linux, Fedora, and Amazon Linux systems, which allow you to -install OpenTofu using the `yum install` or `dnf install` commands. - -If you are instead using Debian or Ubuntu, you -might prefer to [install OpenTofu from our APT repositories](/docs/cli/install/apt). - -## Repository Configuration - -Before adding a repository you must determine which distribution you are using. -The following command lines refer to a placeholder variable `$release` which -you must replace with the appropriate value from the following list: - -* Red Hat Enterprise Linux: `RHEL` -* Fedora: `fedora` -* Amazon Linux: `AmazonLinux` - -If you are using a Yum-based distribution, add the repository using -`yum-config-manager` as follows: - -```bash -sudo yum install -y yum-utils -sudo yum-config-manager --add-repo https://rpm.releases.placeholderplaceholderplaceholder.com/$release/hashicorp.repo -``` - -If you are using a DNF-based distribution, add the repository using -`dnf config-manager` as follows: - -```bash -sudo dnf install -y dnf-plugins-core -sudo dnf config-manager --add-repo https://rpm.releases.placeholderplaceholderplaceholder.com/$release/hashicorp.repo -``` - -In both cases, the OpenTofu package name is `tofu`. For example: - -```bash -yum install tofu -``` - -## Supported Architectures - -The OpenTofu Yum/DNF server has packages only for the `x86_64` -architecture, which is also sometimes known as `amd64`. - -There are no official packages available for other architectures, such as -`aarch64`. If you wish to use OpenTofu on a non-`x86_64` system, -[download a normal release `.zip` file](/docs/downloads) instead. - -## Supported Distribution Releases - -The OpenTofu Yum server contains release repositories for the -following distribution releases: - -* AmazonLinux 2 and "latest" -* Fedora 33 -* Fedora 34 -* Fedora 35 -* Fedora 36 -* Fedora 37 -* RHEL 7 (and CentOS 7) -* RHEL 8 (and CentOS 8) -* RHEL 9 (and CentOS 9) - -No repositories are available for other versions of these distributions or for -any other RPM-based Linux distributions. If you add the repository using -the above commands on other systems then you will see a 404 Not Found error. - -Over time we will change the set of supported distributions, including both -adding support for new releases and ceasing to publish new OpenTofu versions -under older releases. - -## Choosing OpenTofu Versions - -The OpenTofu Yum repositories contain multiple versions of OpenTofu, but -because the packages are all named `tofu` it is impossible to install -more than one version at a time, and `yum install` or `dnf install` will -default to selecting the latest version. - -It's often necessary to match your OpenTofu version with what a particular -configuration is currently expecting. Use the following command to -retrieve the available versions in the repository index: - -```bash -yum --showduplicate list tofu -``` - -You can select a specific version to install by including it in the -`yum install` command line, as follows: - -```bash -yum install tofu-0.14.0-2.x86_64 -``` - -If you are using a DNF-based distribution, similar use `dnf` instead of `yum` -when following the above steps. - -If your workflow requires using multiple versions of OpenTofu at the same -time, for example when working through a gradual upgrade where not all -of your configurations are upgraded yet, we recommend that you use the -official release `.zip` files instead of the Yum packages, so you can install -multiple versions at once and then select which to use for each command you -run.