feat: Add uninstall demo/stack feature

Cargo.toml

@@ -28,8 +28,10 @@ clap = { version = "4.5", features = ["derive", "env"] }
 clap_complete = "4.5"
 clap_complete_nushell = "4.5"
 comfy-table = { version = "7.1", features = ["custom_styling"] }
+dialoguer = "0.12.0"
 directories = "6.0"
 dotenvy = "0.15"
+either = "1.15.0"
 futures = "0.3"
 indexmap = { version = "2.2", features = ["serde"] }
 indicatif = "0.18"
@@ -49,7 +51,7 @@ serde_json = "1.0"
 serde_yaml = "0.9"
 sha2 = "0.10"
 snafu = { version = "0.9", features = ["futures"] }
-stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.108.0", default-features = false, features = ["crds", "kube-ws"] }
+stackable-operator = { git = "https://github.com/stackabletech/operator-rs.git", tag = "stackable-operator-0.109.0", default-features = false, features = ["crds", "kube-ws"] }
 tera = "1.20"
 termion = "4.0"
 tokio = { version = "1.38", features = ["rt-multi-thread", "macros", "fs", "process", "io-std"] }

docs/modules/stackablectl/pages/commands/demo.adoc

@@ -159,4 +159,31 @@ $ stackablectl stacklets list
 
 == Uninstalling a Demo
 
-Currently, there is no support for uninstalling a demo again. However, this functionality will come soon.
+To uninstall a demo, you can run the following command, specifying the namespace the demo was installed in.
+
+[source,console]
+----
+$ stackablectl demo uninstall trino-taxi-data -n <NAMESPACE>
+
+----
+
+[NOTE]
+====
+The uninstall command deletes the namespace the demo was installed in. Therefore it is not possible to uninstall demos in the `default` namespace.
+====
+
+[WARNING]
+====
+Currently, some resources deployed by the demo are either still lingering after the deletion process or need to be deleted before running the uninstall command.
+
+* All demos
+  ** MutatingWebhookConfiguration `restarter-sts-enricher.stackable.tech` is not deleted
+* end-to-end-security, argo-cd-git-ops, hbase-hdfs-load-cycling-data, jupyterhub-pyspark-hdfs-anomaly-detection-taxi-data
+  ** ClusterroleBinding `hdfs-clusterrolebinding-nodes` is not deleted
+* argo-cd-git-ops
+  ** Delete the ArgoCD Applications `airflow`, `airflow-postgres`, `minio`, and `sealed-secrets`
+  ** Then you can delete the namespaces `stackable-airflow`, `minio`, and `sealed-secrets`
+  ** Delete the ArgoCD ApplicationSet `stackable-operators` and wait for ArgoCD to delete the Applications of that ApplicationSet
+  ** Only after deleting the above, run the `stackablectl demo uninstall` command, otherwise the deletion might get stuck
+  ** `*.argoproj.io` CRDs and `sealedsecrets.bitnami.com` CRD are not deleted
+====

docs/modules/stackablectl/pages/commands/stack.adoc

@@ -89,3 +89,39 @@ Installed stack logging
 Use "stackablectl operator installed" to display the installed operators
 Use "stackablectl stacklet list" to display the installed stacklets
 ----
+
+== Uninstalling a Stack
+
+To uninstall a stack, you can run the following command, specifying the namespace the stack was installed in.
+
+[source,console]
+----
+$ stackablectl stack uninstall logging -n <NAMESPACE>
+
+----
+
+[NOTE]
+====
+The uninstall command deletes the namespace the stack was installed in. Therefore it is not possible to uninstall stacks in the `default` namespace.
+====
+
+[WARNING]
+====
+Currently, some resources deployed by the stack are either still lingering after the deletion process or need to be deleted before running the uninstall command.
+
+* All stacks
+  ** MutatingWebhookConfiguration `restarter-sts-enricher.stackable.tech` is not deleted
+* argo-cd-git-ops, hdfs-hbase, jupyterhub-pyspark-hdfs
+  ** ClusterroleBinding `hdfs-clusterrolebinding-nodes` is not deleted
+* argo-cd-git-ops
+  ** Delete the ArgoCD Applications `airflow`, `airflow-postgres`, `minio`, and `sealed-secrets`
+  ** Then you can delete the namespaces `stackable-airflow`, `minio`, and `sealed-secrets`
+  ** Delete the ArgoCD ApplicationSet `stackable-operators` and wait for ArgoCD to delete the Applications of that ApplicationSet
+  ** Only after deleting the above, run the `stackablectl stack uninstall` command, otherwise the deletion might get stuck
+  ** `*.argoproj.io` CRDs and `sealedsecrets.bitnami.com` CRD are not deleted
+* monitoring
+  ** `*.monitoring.coreos.com` CRDs are not deleted
+* observability
+  ** Delete OpenTelemetryCollector `otel-collector-grpc-external` and `otel-collector-grpc`
+  ** Only after deleting the above, run the `stackablectl stack uninstall` command, otherwise the deletion might get stuck
+====

docs/modules/stackablectl/partials/commands/demo.adoc

@@ -6,10 +6,11 @@ Interact with demos, which are end-to-end usage demonstrations of the Stackable
 Usage: stackablectl demo [OPTIONS] <COMMAND>
 
 Commands:
-  list      List available demos
-  describe  Print out detailed demo information
-  install   Install a specific demo
-  help      Print this message or the help of the given subcommand(s)
+  list       List available demos
+  describe   Print out detailed demo information
+  install    Install a specific demo
+  uninstall  Uninstall a specific stack. Caution: This will delete the provided stack namespace, the operators and provided operator namespace, and all Stackable CRDs
+  help       Print this message or the help of the given subcommand(s)
 
 Options:
   -l, --log-level <LOG_LEVEL>

docs/modules/stackablectl/partials/commands/stack.adoc

@@ -6,10 +6,11 @@ Interact with stacks, which are ready-to-use product combinations
 Usage: stackablectl stack [OPTIONS] <COMMAND>
 
 Commands:
-  list      List available stacks
-  describe  Describe a specific stack
-  install   Install a specific stack
-  help      Print this message or the help of the given subcommand(s)
+  list       List available stacks
+  describe   Describe a specific stack
+  install    Install a specific stack
+  uninstall  Uninstall a specific stack. Caution: This will delete the provided stack namespace, the operators and provided operator namespace, and all Stackable CRDs
+  help       Print this message or the help of the given subcommand(s)
 
 Options:
   -l, --log-level <LOG_LEVEL>