Răsfoiți Sursa

[DOCS] Remove unused widgets (#98953)

No-op change to remove a few unused Asciidoc widgets. These aren't referenced or published anywhere in the docs.
James Rodewig 2 ani în urmă
părinte
comite
73293dca86

+ 0 - 40
docs/reference/tab-widgets/quick-start-cleanup-widget.asciidoc

@@ -1,40 +0,0 @@
-++++
-<div class="tabs" data-tab-group="host">
-  <div role="tablist" aria-label="Clean up your deployment">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="cloud-tab-cleanup"
-            id="cloud-cleanup">
-      Elasticsearch Service
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="self-managed-tab-cleanup"
-            id="self-managed-cleanup"
-            tabindex="-1">
-      Self-managed
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="cloud-tab-cleanup"
-       aria-labelledby="cloud-cleanup">
-++++
-
-include::quick-start-cleanup.asciidoc[tag=cloud]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="self-managed-tab-cleanup"
-       aria-labelledby="self-managed-cleanup"
-       hidden="">
-++++
-
-include::quick-start-cleanup.asciidoc[tag=self-managed]
-
-++++
-  </div>
-</div>
-++++

+ 0 - 24
docs/reference/tab-widgets/quick-start-cleanup.asciidoc

@@ -1,24 +0,0 @@
-
-// tag::cloud[]
-Click **Delete deployment** from the deployment overview page and follow the
-prompts.
-// end::cloud[]
-
-// tag::self-managed[]
-To stop your {es} and {kib} Docker containers, run:
-
-[source,sh]
-----
-docker stop es01
-docker stop kibana
-----
-
-To remove the containers and their network, run:
-
-[source,sh]
-----
-docker network rm elastic
-docker rm es01
-docker rm kibana
-----
-// end::self-managed[]

+ 0 - 40
docs/reference/tab-widgets/quick-start-install-widget.asciidoc

@@ -1,40 +0,0 @@
-++++
-<div class="tabs" data-tab-group="host">
-  <div role="tablist" aria-label="Run Elasticsearch">
-    <button role="tab"
-            aria-selected="true"
-            aria-controls="cloud-tab-install"
-            id="cloud-install">
-      Elasticsearch Service
-    </button>
-    <button role="tab"
-            aria-selected="false"
-            aria-controls="self-managed-tab-install"
-            id="self-managed-install"
-            tabindex="-1">
-      Self-managed
-    </button>
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="cloud-tab-install"
-       aria-labelledby="cloud-install">
-++++
-
-include::quick-start-install.asciidoc[tag=cloud]
-
-++++
-  </div>
-  <div tabindex="0"
-       role="tabpanel"
-       id="self-managed-tab-install"
-       aria-labelledby="self-managed-install"
-       hidden="">
-++++
-
-include::quick-start-install.asciidoc[tag=self-managed]
-
-++++
-  </div>
-</div>
-++++

+ 0 - 88
docs/reference/tab-widgets/quick-start-install.asciidoc

@@ -1,88 +0,0 @@
-
-// tag::cloud[]
-include::{docs-root}/shared/cloud/ess-getting-started.asciidoc[tag=generic]
-
-. Click **Continue** to open {kib}.
-
-. Click **Explore on my own**.
-// end::cloud[]
-
-// tag::self-managed[]
-**Install and run {es}**
-
-ifeval::["{release-state}"=="unreleased"]
-NOTE: No Docker image is currently available for {es} {version}.
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-. Install and start https://www.docker.com/products/docker-desktop[Docker
-Desktop].
-
-. Run:
-+
-[source,sh,subs="attributes"]
-----
-docker network create elastic
-docker pull {docker-repo}:{version}
-docker run --name es01 --net elastic -p 9200:9200 -p 9300:9300 -it {docker-image}
-----
-+
-When you start {es} for the first time, the following security configuration 
-occurs automatically:
-+
---
-* <<elasticsearch-security-certificates,Certificates and keys>> are generated
-for the transport and HTTP layers.
-* The Transport Layer Security (TLS) configuration settings are written to
-`elasticsearch.yml`.
-* A password is generated for the `elastic` user.
-* An enrollment token is generated for {kib}.
-
-NOTE: You might need to scroll back a bit in the terminal to view the password 
-and enrollment token.
---
-
-. Copy the generated password and enrollment token and save them in a secure 
-location. These values are shown only when you start {es} for the first time.
-You'll use these to enroll {kib} with your {es} cluster and log in.
-+
-[NOTE]
-====
-If you need to reset the password for the `elastic` user or other
-built-in users, run the <<reset-password,`elasticsearch-reset-password`>> tool.
-To generate new enrollment tokens for {kib} or {es} nodes, run the
-<<create-enrollment-token,`elasticsearch-create-enrollment-token`>> tool.
-These tools are available in the {es} `bin` directory.
-====
-endif::[]
-
-**Install and run {kib}**
-
-To analyze, visualize, and manage {es} data using an intuitive UI, install
-{kib}.
-
-ifeval::["{release-state}"=="unreleased"]
-NOTE: No Docker image is currently available for {kib} {version}.
-endif::[]
-
-ifeval::["{release-state}"!="unreleased"]
-
-. In a new terminal session, run:
-+
-["source","txt",subs="attributes"]
-----
-docker pull docker.elastic.co/kibana/kibana:{version}
-docker run --name kibana --net elastic -p 5601:5601 docker.elastic.co/kibana/kibana:{version}
-----
-+
-When you start {kib}, a unique link is output to your terminal.
-
-. To access {kib}, click the generated link in your terminal.
-
-  .. In your browser, paste the enrollment token that you copied and click the button to connect your {kib} instance with {es}.
-
-  .. Log in to {kib} as the `elastic` user with the password that was generated when you started {es}.
-
-endif::[]
-// end::self-managed[]