feat: move use cases to connections

docs/usecases/aws-resources.md → docs/connections/aws-resources.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 11
-slug: /usecases/aws-resources
+slug: /connections/aws-resources
 ---
 
 # AWS | resources

docs/usecases/ecs-exec-oneoff.md → docs/connections/ecs-exec.md

@@ -1,11 +1,11 @@
 ---
-sidebar_position: 10
-slug: /usecases/ecs-exec-oneoff
+sidebar_position: 11
+slug: /connections/ecs-exec
 ---
 
-# AWS ECS | exec one-off
+# AWS ECS
 
-The Elastic Container Service allows executing one off tasks of any type directly into ECS tasks/containers.
+Interact with Elastic Container Service executing one off tasks or an interactive session into ECS tasks/containers.
 
 :::info note
 It's important to configure the ECS tasks before trying this feature, please refer to the [AWS documentation first](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html)
@@ -21,13 +21,39 @@ It's important to configure the ECS tasks before trying this feature, please ref
 | `AWS_SECRET_ACCESS_KEY` | env-var | The secret key credential          |
 | `AWS_DEFAULT_REGION`    | env-var | The AWS region                     |
 
+## AWS ECS - Interactive Sessions
+
+The AWS Elastic Container Service allows connecting to tasks and starting interactive sessions. It's possible to map these commands to Hoop to obtain interactive sessions allocating a pseudo TTY.
+
+:::info note
+It's important to configure the ECS tasks before trying this feature, please refer to the [AWS documentation first](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html)
+:::
+
+### Connection Command
+
+```shell
+ecs-exec.sh --interactive --cluster=$CLUSTER_NAME --service-name=$SERVICE_NAME
+```
+
+### How to Use
+
+Start an interactive session 
+
+```shell
+hoop connect my-ecs -- --pipe /bin/bash
+hoop connect my-ecs -- --pipe 'rails console'
+hoop connect my-ecs -- --pipe clojure
+```
+
+## AWS ECS - Execute one task off
+
 ### Connection Command
 
 ```shell
 ecs-exec.sh --cluster=$CLUSTER_NAME --service-name=$SERVICE_NAME
 ```
 
-## How to Use
+### How to Use
 
 Now it's possible to execute ruby script straight from Hoop
 

docs/usecases/heroku-oneoff.mdx → docs/connections/heroku-oneoff.mdx

@@ -1,11 +1,11 @@
 ---
-sidebar_position: 7
-slug: /usecases/heroku-oneoff
+sidebar_position: 20
+slug: /connections/heroku-oneoff
 ---
 
 import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton';
 
-# Heroku one-off
+# Heroku execute task one-off
 
 <ConnectOnHoopButton url='https://app.hoop.dev/connections/command-line/new?data=ewogICAgIm5hbWUiOiJteS1oZXJva3Utb25lLW9mZiIsCiAgICAidHlwZSI6ImNvbW1hbmQtbGluZSIsCiAgICAiaWNvbl9uYW1lIjogImhlcm9rdSIsCiAgICAic2VjcmV0IjogewogICAgICAgICJlbnZ2YXI6SEVST0tVX0FQSV9LRVkiOiIiCiAgICB9LAogICAgImNvbW1hbmQiOiBbIi9hcHAvYmluL2hlcm9rdSIsICJydW4iLCAiLS1leGl0LWNvZGUiXQp9' />
 

docs/usecases/heroku-psexec.mdx → docs/connections/heroku-psexec.mdx

@@ -1,11 +1,11 @@
 ---
-sidebar_position: 8
-slug: /usecases/heroku-psexec
+sidebar_position: 20
+slug: /connections/heroku-psexec
 ---
 
 import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton';
 
-# Heroku | exec
+# Heroku | interactive
 
 <ConnectOnHoopButton url='https://app.hoop.dev/connections/command-line/new?data=ewogICAgIm5hbWUiOiJteS1oZXJva3UtZXhlYyIsCiAgICAidHlwZSI6ImNvbW1hbmQtbGluZSIsCiAgICAiaWNvbl9uYW1lIjogImhlcm9rdSIsCiAgICAic2VjcmV0IjogewogICAgICAgICJlbnZ2YXI6SEVST0tVX0FQSV9LRVkiOiIiCiAgICB9LAogICAgImNvbW1hbmQiOiBbIi9hcHAvYmluL3BzLWV4ZWMuc2giXQp9' />
 

docs/usecases/forwarding-http.md → docs/connections/http.md

@@ -1,9 +1,9 @@
 ---
-sidebar_position: 3
-slug: /usecases/forwarding-http
+sidebar_position: 2
+slug: /connections/http
 ---
 
-# Port Forward | http
+# Http
 
 Port Forward local ports from your private network | HTTP example.
 

docs/connections/index.md

@@ -2,6 +2,8 @@
 
 Connect and interact with your internal services.
 
+Quickstart about how to connect hoop with the services.
+
 ```mdx-code-block
 import DocCardList from '@theme/DocCardList';
 

docs/usecases/kubernetes-exec.mdx → docs/connections/kubernetes-exec.mdx

@@ -1,11 +1,11 @@
 ---
-sidebar_position: 4
-slug: /usecases/k8s-exec
+sidebar_position: 7
+slug: /usecases/k8s/exec
 ---
 
 import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton';
 
-# Kubernetes | exec
+# Kubernetes
 
 <ConnectOnHoopButton url='https://app.hoop.dev/connections/command-line/new?data=ewogICAgIm5hbWUiOiJteS1rdWJlcm5ldHMtZXhlYyIsCiAgICAidHlwZSI6ImNvbW1hbmQtbGluZSIsCiAgICAiaWNvbl9uYW1lIjogImt1YmVybmV0ZXMiLAogICAgInNlY3JldCI6IHsKICAgICAgICAiZmlsZXN5c3RlbTpLVUJFQ09ORklHIjoiIiwKICAgICAgICAiZW52dmFyOkRFUExPWV9OQU1FIjogIiIsCiAgICAgICAgImVudnZhcjpOQU1FU1BBQ0UiOiAiIgogICAgfSwKICAgICJjb21tYW5kIjogWyJrdWJlY3RsIiwgImV4ZWMiLCAiLS10dHkiLCAiLS1zdGRpbiIsICIkREVQTE9ZX05BTUUiLCAiLS1uYW1lc3BhY2UiLCAiJE5BTUVTUEFDRSIsICItLSJdCn0=' />
 

docs/usecases/kubernetes-oneoff.mdx → docs/connections/kubernetes-oneoff.mdx

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 5
-slug: /usecases/k8s-oneoff
+sidebar_position: 7
+slug: /usecases/k8s/oneoff
 ---
 
 import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton';

docs/usecases/kubernetes-resources.md → docs/connections/kubernetes-resources.md

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 6
-slug: /usecases/k8s-resources
+sidebar_position: 7
+slug: /usecases/k8s/resources
 ---
 
 # Kubernetes | resources
@@ -23,11 +23,11 @@ kubectl
 
 ```shell
 # view pods in the default namespace
-hoop exec k8s -- get pods
+hoop exec my-conn-k8s -- get pods
 # restart an app
 hoop exec k8s -- rollout restart deployment/myapp
 # scale up an app
-hoop exec k8s -- scale --replicas=3 deployment/myapp
+hoop exec my-conn-k8s -- scale --replicas=3 deployment/myapp
 ```
 
 It's possible to narrow down the commands in distinct connections, this gives a better user experience
@@ -41,6 +41,6 @@ kubectl --namespace prod rollout
 Then it's possible
 
 ```shell
-hoop exec k8s -- restart deployment/myapp
-hoop exec k8s -- undo deployment/myapp
+hoop exec my-conn-k8s -- restart deployment/myapp
+hoop exec my-conn-k8s -- undo deployment/myapp
 ```

docs/usecases/mongodb.md → docs/connections/mongodb.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 16
-slug: /usecases/mongodb
+slug: /connections/mongodb
 ---
 
 # MongoDB | mongosh cli

docs/usecases/mysqlcli.md → docs/connections/mysql-cli.md

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 14
-slug: /usecases/mysqlcli
+sidebar_position: 3
+slug: /connections/mysqlcli
 ---
 
 # MySQL | mysql cli

docs/connections/native/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Native Connections",
+  "position": 1
+}

docs/connections/command-line.mdx → docs/connections/native/command-line.mdx

@@ -1,9 +1,9 @@
 ---
 sidebar_position: 1
-slug: /connections/command-line
+slug: /connections/native/command-line
 ---
 
-import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton';
+import ConnectOnHoopButton from './../../../src/components/ConnectOnHoopButton';
 
 # Command Line
 

docs/connections/port-forward.mdx → docs/connections/native/port-forward.mdx

@@ -1,9 +1,9 @@
 ---
 sidebar_position: 2
-slug: /connections/port-forward
+slug: /connections/native/port-forward
 ---
 
-import ConnectOnHoopButton from './../../src/components/ConnectOnHoopButton';
+import ConnectOnHoopButton from './../../../src/components/ConnectOnHoopButton';
 
 # Port Forward
 

docs/usecases/psql.md → docs/connections/postgres-psql.md

@@ -1,9 +1,9 @@
 ---
-sidebar_position: 14
-slug: /usecases/psql
+sidebar_position: 4
+slug: /connections/psql
 ---
 
-# Postgres | psql cli
+# Postgres | psql cli 
 
 An optional way to connect into postgres is using the `psql` client. It's possible to create a interactive session or execute one-off commands.
 

docs/connections/postgres.mdx

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 5
 slug: /connections/postgres
 ---
 

docs/usecases/postgres.md → docs/connections/postgres.txt

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 13
-slug: /usecases/postgres
+sidebar_position: 5
+slug: /connections/postgres-psql
 ---
 
 # Postgres

docs/usecases/scripts.md → docs/connections/scripts.md

@@ -1,9 +1,9 @@
 ---
 sidebar_position: 16
-slug: /usecases/scripts
+slug: /connections/scripts
 ---
 
-# Scripts | one-off
+# Execute scripts with Hoop connections
 
 Allows executing one-off scripts using the underlying Operating System tools.
 

docs/usecases/sqlserver.md → docs/connections/sqlserver.md

@@ -1,6 +1,6 @@
 ---
-sidebar_position: 15
-slug: /usecases/sqlserver
+sidebar_position: 6
+slug: /connections/sqlserver
 ---
 
 # SQL Server | sqlcmd cli

docs/usecases/ssh-bastion.md → docs/connections/ssh-bastion.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 17
-slug: /usecases/bastion
+slug: /connections/bastion
 ---
 
 # Bastion Server | ssh cli

docs/installing-hoop-agent/heroku.mdx

@@ -76,5 +76,5 @@ After disconnecting it, check if there's any recorded session available at **htt
 See how to use the heroku cli through Hoop.
 
 - [Heroku Management Guide](../tutorials/heroku-exec.mdx)
-- [Heroku ps:exec](../usecases/heroku-psexec.mdx)
-- [Heroku one-off](../usecases/heroku-oneoff.mdx)
+- [Heroku ps:exec](../connections/heroku-psexec.mdx)
+- [Heroku one-off](../connections/heroku-oneoff.mdx)

docs/setting-up/quickstart-builder.jsx

@@ -7,25 +7,24 @@ import DockerPlatform from './../installing-hoop-agent/docker.mdx';
 import HerokuPlatform from './../installing-hoop-agent/heroku.mdx';
 import KubernetesPlatform from './../installing-hoop-agent/kubernetes.md';
 
-// use cases docs
-import MySQLUseCase from './../usecases/forwarding-mysql.md';
-import MySQLCLIUseCase from './../usecases/mysql.md';
-import NativePostgresUseCase from './../usecases/postgres.md';
-import PostgresPSQLUseCase from './../usecases/psql.md';
-import MongoDBmongoshUseCase from './../usecases/mongodb.md';
-import KubernetesExecUseCase from './../usecases/kubernetes-exec.mdx';
-import KubernetesResourcesUseCase from './../usecases/kubernetes-resources.md';
-import HerokuExecUseCase from './../usecases/heroku-oneoff.mdx';
-import HerokuInteractiveUseCase from './../usecases/heroku-psexec.mdx';
-import AWSExecUseCase from './../usecases/ecs-exec.md';
-import AWSResourcesUseCase from './../usecases/aws-resources.md';
-import SQLServerCLIUseCase from './../usecases/sqlserver.md';
-import BastionServerUseCase from './../usecases/ssh-bastion.md';
-import PortForwardHTTPUseCase from './../usecases/forwarding-http.md';
+// use cases docs --> moved to connections
+import MySQLCLIUseCase from './../connections/mysql-cli.md';
+import NativePostgresUseCase from './../connections/postgres-psql.md';
+import PostgresPSQLUseCase from './../connections/postgres-psql.md';
+import MongoDBmongoshUseCase from './../connections/mongodb.md';
+import KubernetesExecUseCase from './../connections/kubernetes-exec.mdx';
+import KubernetesResourcesUseCase from './../connections/kubernetes-resources.md';
+import HerokuExecUseCase from './../connections/heroku-oneoff.mdx';
+import HerokuInteractiveUseCase from './../connections/heroku-psexec.mdx';
+import AWSExecUseCase from './../connections/ecs-exec.md';
+import AWSResourcesUseCase from './../connections/aws-resources.md';
+import SQLServerCLIUseCase from './../connections/sqlserver.md';
+import BastionServerUseCase from './../connections/ssh-bastion.md';
+import PortForwardHTTPUseCase from './../connections/http.md';
 
 // connections
-import CommandLineConnection from './../connections/command-line.mdx';
-import PortForwardConnection from './../connections/port-forward.mdx';
+import CommandLineConnection from './../connections/native/command-line.mdx';
+import PortForwardConnection from './../connections/native/port-forward.mdx';
 import PostgresConnection from './../connections/postgres.mdx';
 
 const docOptions = {