website: Remove pages for atlas backend and terraform push

These pages are already deleted in the 0.15 docs, and prolonging their life in
the 0.14 docs would add unnecessary complexity to this URL migration, so let's
just axe them early.

website/docs/backends/types/terraform-enterprise.html.md

@@ -1,68 +0,0 @@
----
-layout: "language"
-page_title: "Backend Type: terraform enterprise"
-sidebar_current: "docs-backends-types-standard-terraform-enterprise"
-description: |-
-  Terraform can store its state in Terraform Enterprise
----
-
-# terraform enterprise
-
-!> **The `atlas` backend is deprecated.** Please use the new enhanced
-[remote](/docs/backends/types/remote.html) backend for storing state and running
-remote operations in Terraform Cloud.
-
-**Kind: Standard (with no locking)**
-
-Reads and writes state from a [Terraform Enterprise](/docs/cloud/index.html)
-workspace.
-
--> **Why is this called "atlas"?** Before it was a standalone offering,
-Terraform Enterprise was part of an integrated suite of enterprise products
-called Atlas. This backend predates the current version Terraform Enterprise, so
-it uses the old name.
-
-We no longer recommend using this backend, as it does not support collaboration
-features like [workspace
-locking](/docs/cloud/run/index.html). Please use the new enhanced
-[remote](/docs/backends/types/remote.html) backend for storing state and running
-remote operations in Terraform Cloud.
-
-## Example Configuration
-
-```hcl
-terraform {
-  backend "atlas" {
-    name = "example_corp/networking-prod"
-    address = "https://app.terraform.io" # optional
-  }
-}
-```
-
-We recommend using a [partial configuration](/docs/backends/config.html) and
-omitting the access token, which can be provided as an environment variable.
-
-## Data Source Configuration
-
-```hcl
-data "terraform_remote_state" "foo" {
-  backend = "atlas"
-  config = {
-    name = "example_corp/networking-prod"
-  }
-}
-```
-
-## Configuration variables
-
-The following configuration options / environment variables are supported:
-
-* `name` - (Required) Full name of the workspace (`<ORGANIZATION>/<WORKSPACE>`).
-* `ATLAS_TOKEN`/ `access_token`  - (Optional) A Terraform Enterprise [user API
-  token](/docs/cloud/users-teams-organizations/users.html#api-tokens). We
-  recommend using the `ATLAS_TOKEN` environment variable rather than setting
-  `access_token` in the configuration. If not set, the token will be requested
-  during a `terraform init` and saved locally.
-* `address` - (Optional) The URL of a Terraform Enterprise instance. Defaults to
-  the SaaS version of Terraform Enterprise, at `"https://app.terraform.io"`; if
-  you use a private install, provide its URL here.

website/docs/configuration/terraform-enterprise.html.md

@@ -1,31 +0,0 @@
----
-layout: "docs"
-page_title: "Configuring Terraform Push"
-sidebar_current: "docs-config-push"
-description: |-
-  Terraform's push command was a way to interact with the legacy version of Terraform Enterprise. It is not supported in the current version of Terraform Enterprise.
----
-
-# Terraform Push Configuration
-
--> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
-earlier, see
-[0.11 Configuration Language: Configuring Terraform Push](../configuration-0-11/terraform-enterprise.html).
-
-Prior to v0.12, Terraform included mechanisms to interact with a legacy version
-of Terraform Enterprise, formerly known as "Atlas".
-
-These features relied on a special configuration block named `atlas`:
-
-```hcl
-atlas {
-  name = "acme-corp/production"
-}
-```
-
-These features are no longer available on Terraform Enterprise and so the
-corresponding configuration elements and commands have been removed in
-Terraform v0.12.
-
-After upgrading to the current version of Terraform Enterprise,
-any `atlas` blocks in your configuration can be safely removed.