nextmv 1.0.0.dev3__py3-none-any.whl → 1.0.0.dev4__py3-none-any.whl

nextmv/cli/cloud/batch/create.py

@@ -109,7 +109,7 @@ def create(
             "--wait",
             "-w",
             help="Wait for the batch experiment to complete. Results are printed to [magenta]stdout[/magenta]. "
-            "Specify output location with [code]--output[/code].",
+            "Specify output location with --output.",
             rich_help_panel="Output control",
         ),
     ] = False,
@@ -122,21 +122,19 @@ def create(
     configurations. Each run is defined by a combination of input, instance or
     version, and optional configuration options.
 
-    Use the [code]--wait[/code] flag to wait for the batch experiment to
-    complete, polling for results. Using the [code]--output[/code] flag will
-    also activate waiting, and allows you to specify a destination file for the
-    results.
+    Use the --wait flag to wait for the batch experiment to complete, polling
+    for results. Using the --output flag will also activate waiting, and allows
+    you to specify a destination file for the results.
 
     [bold][underline]Runs[/underline][/bold]
 
-    Runs are provided as [magenta]json[/magenta] objects using the
-    [code]--runs[/code] flag. Each run defines what input, instance/version,
-    and configuration to use.
+    Runs are provided as [magenta]json[/magenta] objects using the --runs flag.
+    Each run defines what input, instance/version, and configuration to use.
 
     You can provide runs in three ways:
     - A single run as a [magenta]json[/magenta] object.
-    - Multiple runs by repeating the [code]--runs[/code] flag.
-    - Multiple runs as a [magenta]json[/magenta] array in a single [code]--runs[/code] flag.
+    - Multiple runs by repeating the --runs flag.
+    - Multiple runs as a [magenta]json[/magenta] array in a single --runs flag.
 
     Each run must have the following fields:
     - [magenta]input_id[/magenta]: ID of the input to use for this run
@@ -146,46 +144,46 @@ def create(
     - [magenta]instance_id[/magenta] OR [magenta]version_id[/magenta]: Either an instance ID or
       version ID must be provided (at least one required).
     - [magenta]option_set[/magenta]: ID of the option set to use (optional).
-      Make sure to define the option sets using the [code]--option-sets[/code] flag.
+      Make sure to define the option sets using the --option-sets flag.
     - [magenta]input_set_id[/magenta]: ID of the input set (optional).
     - [magenta]scenario_id[/magenta]: Scenario ID if part of a scenario test (optional).
     - [magenta]repetition[/magenta]: Repetition number (optional).
 
     Object format:
-    [green]{
+    [dim]{
         "input_id": "meadow-input-a1",
         "instance_id": "bunny-hopper-v2",
         "option_set": "speed-optimized",
         "input_set_id": "spring-gardens"
-    }[/green]
+    }[/dim]
 
     [bold][underline]Option Sets[/underline][/bold]
 
     Option sets are provided as a [magenta]json[/magenta] object using the
-    [code]--option-sets[/code] flag. Option sets define named collections of
+    --option-sets flag. Option sets define named collections of
     runtime options that can be referenced by runs.
 
     The option sets object is a dictionary where keys are option set IDs and
     values are dictionaries of string key-value pairs representing the options.
 
     Object format:
-    [green]{
+    [dim]{
         "speed-optimized": {"timeout": "30", "algorithm": "fast"},
         "quality-focused": {"timeout": "300", "algorithm": "thorough"}
-    }[/green]
+    }[/dim]
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create a batch experiment with a single run.
-        $ [green]RUN='{
+        $ [dim]RUN='{
             "input_id": "carrot-patch-a",
             "instance_id": "warren-planner-v1"
         }'
         nextmv cloud batch create --app-id hare-app --batch-experiment-id bunny-hop-test \\
-            --name "Spring Meadow Routes" --input-set-id spring-gardens --runs "$RUN"[/green]
+            --name "Spring Meadow Routes" --input-set-id spring-gardens --runs "$RUN"[/dim]
 
     - Create with multiple runs by repeating the flag.
-        $ [green]RUN1='{
+        $ [dim]RUN1='{
             "input_id": "lettuce-field-1",
             "instance_id": "hop-optimizer"
         }'
@@ -195,10 +193,10 @@ def create(
         }'
         nextmv cloud batch create --app-id hare-app --batch-experiment-id lettuce-routes \\
             --name "Lettuce Delivery Optimization" --input-set-id veggie-gardens \\
-            --runs "$RUN1" --runs "$RUN2"[/green]
+            --runs "$RUN1" --runs "$RUN2"[/dim]
 
     - Create with multiple runs in a single [magenta]json[/magenta] array.
-        $ [green]RUNS='[
+        $ [dim]RUNS='[
             {
                 "input_id": "warren-zone-a",
                 "instance_id": "burrow-builder"
@@ -209,28 +207,28 @@ def create(
             }
         ]'
         nextmv cloud batch create --app-id hare-app --batch-experiment-id warren-expansion \\
-            --name "Warren Construction Plans" --input-set-id burrow-sites --runs "$RUNS"[/green]
+            --name "Warren Construction Plans" --input-set-id burrow-sites --runs "$RUNS"[/dim]
 
     - Create a batch experiment and wait for it to complete.
-        $ [green]RUN='{
+        $ [dim]RUN='{
             "input_id": "carrot-harvest",
             "instance_id": "foraging-route"
         }'
         nextmv cloud batch create --app-id hare-app --batch-experiment-id harvest-time \\
             --name "Autumn Carrot Collection" --input-set-id harvest-season \\
-            --runs "$RUN" --wait[/green]
+            --runs "$RUN" --wait[/dim]
 
     - Create a batch experiment and save the results to a file, waiting for completion.
-        $ [green]RUN='{
+        $ [dim]RUN='{
             "input_id": "predator-zones",
             "instance_id": "safe-hopper"
         }'
         nextmv cloud batch create --app-id hare-app --batch-experiment-id safety-analysis \\
             --name "Fox Avoidance Routes" --input-set-id danger-zones \\
-            --runs "$RUN" --output bunny-safety-results.json[/green]
+            --runs "$RUN" --output bunny-safety-results.json[/dim]
 
     - Create a batch experiment with option sets.
-        $ [green]RUN1='{
+        $ [dim]RUN1='{
             "input_id": "garden-route-1",
             "instance_id": "hop-optimizer",
             "option_set": "fast-hops"
@@ -246,7 +244,7 @@ def create(
         }'
         nextmv cloud batch create --app-id hare-app --batch-experiment-id hop-comparison \\
             --name "Speed vs Safety Analysis" --input-set-id garden-paths \\
-            --runs "$RUN1" --runs "$RUN2" --option-sets "$OPTION_SETS"[/green]
+            --runs "$RUN1" --runs "$RUN2" --option-sets "$OPTION_SETS"[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/batch/delete.py

@@ -5,9 +5,9 @@ This module defines the cloud batch delete command for the Nextmv CLI.
 from typing import Annotated
 
 import typer
-from rich.prompt import Confirm
 
 from nextmv.cli.configuration.config import build_app
+from nextmv.cli.confirm import get_confirmation
 from nextmv.cli.message import info, success
 from nextmv.cli.options import AppIDOption, BatchExperimentIDOption, ProfileOption
 
@@ -33,24 +33,23 @@ def delete(
     Deletes a Nextmv Cloud batch experiment.
 
     This action is permanent and cannot be undone. The batch experiment and all
-    associated data, including runs, will be deleted. Use the [code]--yes[/code]
+    associated data, including runs, will be deleted. Use the --yes
     flag to skip the confirmation prompt.
 
     [bold][underline]Examples[/underline][/bold]
 
     - Delete the batch experiment with the ID [magenta]hop-analysis[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud batch delete --app-id hare-app --batch-experiment-id hop-analysis[/green]
+        $ [dim]nextmv cloud batch delete --app-id hare-app --batch-experiment-id hop-analysis[/dim]
 
     - Delete the batch experiment without confirmation prompt.
-        $ [green]nextmv cloud batch delete --app-id hare-app --batch-experiment-id carrot-routes --yes[/green]
+        $ [dim]nextmv cloud batch delete --app-id hare-app --batch-experiment-id carrot-routes --yes[/dim]
     """
 
     if not yes:
-        confirm = Confirm.ask(
+        confirm = get_confirmation(
             f"Are you sure you want to delete batch experiment [magenta]{batch_experiment_id}[/magenta] "
             f"from application [magenta]{app_id}[/magenta]? This action cannot be undone.",
-            default=False,
         )
 
         if not confirm:

nextmv/cli/cloud/batch/get.py

@@ -42,7 +42,7 @@ def get(
             "--wait",
             "-w",
             help="Wait for the batch experiment to complete. Results are printed to [magenta]stdout[/magenta]. "
-            "Specify output location with [code]--output[/code].",
+            "Specify output location with --output.",
         ),
     ] = False,
     profile: ProfileOption = None,
@@ -50,8 +50,8 @@ def get(
     """
     Get a Nextmv Cloud batch experiment, including its runs.
 
-    Use the [code]--wait[/code] flag to wait for the batch experiment to
-    complete, polling for results. Using the [code]--output[/code] flag will
+    Use the --wait flag to wait for the batch experiment to
+    complete, polling for results. Using the --output flag will
     also activate waiting, and allows you to specify a destination file for the
     results.
 
@@ -59,17 +59,17 @@ def get(
 
     - Get the batch experiment with ID [magenta]carrot-optimization[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id carrot-optimization[/green]
+        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id carrot-optimization[/dim]
 
     - Get the batch experiment and wait for it to complete if necessary.
-        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id bunny-hop-test --wait[/green]
+        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id bunny-hop-test --wait[/dim]
 
     - Get the batch experiment and save the results to a file.
-        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id warren-planning \\
-            --output results.json[/green]
+        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id warren-planning \\
+            --output results.json[/dim]
 
     - Get the batch experiment using a specific profile.
-        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id lettuce-routes --profile prod[/green]
+        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id lettuce-routes --profile prod[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/batch/list.py

@@ -38,13 +38,13 @@ def list(
     [bold][underline]Examples[/underline][/bold]
 
     - List all batch experiments for application [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud batch list --app-id hare-app[/green]
+        $ [dim]nextmv cloud batch list --app-id hare-app[/dim]
 
     - List all batch experiments and save to a file.
-        $ [green]nextmv cloud batch list --app-id hare-app --output experiments.json[/green]
+        $ [dim]nextmv cloud batch list --app-id hare-app --output experiments.json[/dim]
 
     - List all batch experiments using a specific profile.
-        $ [green]nextmv cloud batch list --app-id hare-app --profile prod[/green]
+        $ [dim]nextmv cloud batch list --app-id hare-app --profile prod[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/batch/metadata.py

@@ -41,14 +41,14 @@ def metadata(
 
     - Get metadata for batch experiment [magenta]bunny-warren-optimization[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id bunny-warren-optimization[/green]
+        $ [dim]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id bunny-warren-optimization[/dim]
 
     - Get metadata and save to a file.
-        $ [green]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id lettuce-delivery \\
-            --output metadata.json[/green]
+        $ [dim]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id lettuce-delivery \\
+            --output metadata.json[/dim]
 
     - Get metadata using a specific profile.
-        $ [green]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id hop-schedule --profile prod[/green]
+        $ [dim]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id hop-schedule --profile prod[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/batch/update.py

@@ -57,17 +57,17 @@ def update(
     [bold][underline]Examples[/underline][/bold]
 
     - Update the name of a batch experiment.
-        $ [green]nextmv cloud batch update --app-id hare-app --batch-experiment-id carrot-feast \\
-            --name "Spring Carrot Harvest"[/green]
+        $ [dim]nextmv cloud batch update --app-id hare-app --batch-experiment-id carrot-feast \\
+            --name "Spring Carrot Harvest"[/dim]
 
     - Update the description of a batch experiment.
-        $ [green]nextmv cloud batch update --app-id hare-app --batch-experiment-id bunny-hop-routes \\
-            --description "Optimizing hop paths through the meadow"[/green]
+        $ [dim]nextmv cloud batch update --app-id hare-app --batch-experiment-id bunny-hop-routes \\
+            --description "Optimizing hop paths through the meadow"[/dim]
 
     - Update both name and description and save the result.
-        $ [green]nextmv cloud batch update --app-id hare-app --batch-experiment-id lettuce-delivery \\
+        $ [dim]nextmv cloud batch update --app-id hare-app --batch-experiment-id lettuce-delivery \\
             --name "Warren Lettuce Express" --description "Fast lettuce delivery to all burrows" \\
-            --output updated-batch.json[/green]
+            --output updated-batch.json[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/data/__init__.py

@@ -14,7 +14,7 @@ app.add_typer(upload_app)
 @app.callback()
 def callback() -> None:
     """
-    Upload data for Nextmv Cloud application runs.
+    Upload data for Nextmv Cloud application components.
 
     When data is too large (exceeds [magenta]5 MiB[/magenta]), or you are
     working with the [magenta]multi-file[/magenta] content format, you can use

nextmv/cli/cloud/data/upload.py

@@ -45,29 +45,29 @@ def upload(
     profile: ProfileOption = None,
 ) -> None:
     """
-    Upload data for Nextmv Cloud application runs.
+    Upload data for Nextmv Cloud application components.
 
     When data is too large, or is not in a text-based content format, you can
     use this command to upload information for a Nextmv Cloud application. Data
     is used for starting new runs, tracking runs, performing experiments, and
     more.
 
-    The [code]--upload-url[/code] flag is required to specify the pre-signed
+    The --upload-url flag is required to specify the pre-signed
     upload URL. It can be obtained using the [code]nextmv cloud upload
     create[/code] command. Use the [magenta].upload_url[/magenta] field from
     the command output.
 
     The data input should be given through [magenta]stdin[/magenta] or the
-    [code]--input[/code] flag. When using the [code]--input[/code] flag, the
-    value can be one of the following:
+    --input flag. When using the --input flag, the value can be one of the
+    following:
 
-    - [green]<FILE_PATH>[/green]: path to a [magenta]file[/magenta] containing
+    - [yellow]<FILE_PATH>[/yellow]: path to a [magenta]file[/magenta] containing
       the data. Use with the [magenta]json[/magenta], and
       [magenta]text[/magenta] content formats.
-    - [green]<DIR_PATH>[/green]: path to a [magenta]directory[/magenta]
+    - [yellow]<DIR_PATH>[/yellow]: path to a [magenta]directory[/magenta]
       containing data files. Use with the [magenta]multi-file[/magenta]
       content format.
-    - [green]<.tar.gz_PATH>[/green]: path to a [magenta].tar.gz[/magenta] file
+    - [yellow]<.tar.gz PATH>[/yellow]: path to a [magenta].tar.gz[/magenta] file
       containing tarred data files. Use with the [magenta]multi-file[/magenta]
       content format.
 
@@ -75,30 +75,30 @@ def upload(
 
     - Upload data from [magenta]stdin[/magenta] for application
       [magenta]hare-app[/magenta].
-        $ [green]echo '{"key": "value"}' | nextmv cloud data upload --app-id hare-app --upload-url <URL>[/green]
+        $ [dim]echo '{"key": "value"}' | nextmv cloud data upload --app-id hare-app --upload-url <URL>[/dim]
 
     - Upload data from a [magenta]JSON[/magenta] file.
-        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json[/green]
+        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json[/dim]
 
     - Upload data from a [magenta]text[/magenta] file.
-        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.txt[/green]
+        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.txt[/dim]
 
     - Upload [magenta]multi-file[/magenta] data from a directory.
-        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input ./data_directory[/green]
+        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input ./data_directory[/dim]
 
     - Upload [magenta]multi-file[/magenta] data from a
       [magenta].tar.gz[/magenta] file.
-        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.tar.gz[/green]
+        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.tar.gz[/dim]
 
     - Upload data using a specific profile.
-        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json \\
-            --profile production[/green]
+        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json \\
+            --profile production[/dim]
     """
 
     # Validate that input is provided.
     stdin = sys.stdin.read().strip() if sys.stdin.isatty() is False else None
     if stdin is None and (input is None or input == ""):
-        error("Input data must be provided via the [code]--input[/code] flag or [magenta]stdin[/magenta].")
+        error("Input data must be provided via the --input flag or [magenta]stdin[/magenta].")
 
     cloud_app = build_app(app_id=app_id, profile=profile)
     data_kwarg = resolve_data_kwarg(

nextmv/cli/cloud/ensemble/__init__.py

@@ -7,6 +7,7 @@ import typer
 from nextmv.cli.cloud.ensemble.create import app as create_app
 from nextmv.cli.cloud.ensemble.delete import app as delete_app
 from nextmv.cli.cloud.ensemble.get import app as get_app
+from nextmv.cli.cloud.ensemble.list import app as list_app
 from nextmv.cli.cloud.ensemble.update import app as update_app
 
 # Set up subcommand application.
@@ -14,6 +15,7 @@ app = typer.Typer()
 app.add_typer(create_app)
 app.add_typer(delete_app)
 app.add_typer(get_app)
+app.add_typer(list_app)
 app.add_typer(update_app)
 
 

nextmv/cli/cloud/ensemble/create.py

@@ -30,13 +30,12 @@ app = typer.Typer()
     [bold][underline]Run Groups[/underline][/bold]
 
     Run groups are provided as [magenta]json[/magenta] objects using the
-    [code]--run-groups[/code] flag. Each run group specifies how child runs
-    are executed.
+    --run-groups flag. Each run group specifies how child runs are executed.
 
     You can provide run groups in three ways:
     - A single run group as a [magenta]json[/magenta] object.
-    - Multiple run groups by repeating the [code]--run-groups[/code] flag.
-    - Multiple run groups as a [magenta]json[/magenta] array in a single [code]--run-groups[/code] flag.
+    - Multiple run groups by repeating the --run-groups flag.
+    - Multiple run groups as a [magenta]json[/magenta] array in a single --run-groups flag.
 
     Each run group must have the following fields:
     - [magenta]id[/magenta]: Unique identifier for the run group (required).
@@ -46,23 +45,23 @@ app = typer.Typer()
     - [magenta]repetitions[/magenta]: Number of times to repeat the run (optional).
 
     Object format:
-    [green]{{
+    [dim]{{
         "id": "rg1",
         "instance_id": "inst-123",
         "options": {{"param": "value"}},
         "repetitions": 5
-    }}[/green]
+    }}[/dim]
 
     [bold][underline]Evaluation Rules[/underline][/bold]
 
     Evaluation rules are provided as [magenta]json[/magenta] objects using the
-    [code]--rules[/code] flag. Each rule determines how to evaluate and select
-    the best result from the child runs.
+    --rules flag. Each rule determines how to evaluate and select the best
+    result from the child runs.
 
     You can provide rules in three ways:
     - A single rule as a [magenta]json[/magenta] object.
-    - Multiple rules by repeating the [code]--rules[/code] flag.
-    - Multiple rules as a [magenta]json[/magenta] array in a single [code]--rules[/code] flag.
+    - Multiple rules by repeating the --rules flag.
+    - Multiple rules as a [magenta]json[/magenta] array in a single --rules flag.
 
     Each rule must have the following fields:
     - [magenta]id[/magenta]: Unique identifier for the rule (required).
@@ -75,18 +74,18 @@ app = typer.Typer()
     - [magenta]index[/magenta]: Evaluation order - lower indices evaluated first (required).
 
     Object format:
-    [green]{{
+    [dim]{{
         "id": "rule1",
         "statistics_path": "$.result.value",
         "objective": "minimize",
         "tolerance": {{"value": 0.1, "type": "relative"}},
         "index": 0
-    }}[/green]
+    }}[/dim]
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create an ensemble definition with a single run group and rule.
-        $ [green]RUN_GROUP='{{
+        $ [dim]RUN_GROUP='{{
             "id": "rg1",
             "instance_id": "inst-123"
         }}'
@@ -97,10 +96,10 @@ app = typer.Typer()
             "tolerance": {{"value": 0.1, "type": "relative"}},
             "index": 0
         }}'
-        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP" --rules "$RULE"[/green]
+        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP" --rules "$RULE"[/dim]
 
     - Create with multiple run groups by repeating the flag.
-        $ [green]RUN_GROUP_1='{{
+        $ [dim]RUN_GROUP_1='{{
             "id": "rg1",
             "instance_id": "inst-123"
         }}'
@@ -117,10 +116,10 @@ app = typer.Typer()
             "index": 0
         }}'
         nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP_1" --run-groups "$RUN_GROUP_2" \\
-            --rules "$RULE"[/green]
+            --rules "$RULE"[/dim]
 
     - Create with multiple items in a single JSON array.
-        $ [green]RUN_GROUPS='[
+        $ [dim]RUN_GROUPS='[
             {{"id": "rg1", "instance_id": "inst-123"}},
             {{"id": "rg2", "instance_id": "inst-456"}}
         ]'
@@ -131,10 +130,10 @@ app = typer.Typer()
             "tolerance": {{"value": 0.1, "type": "relative"}},
             "index": 0
         }}]'
-        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUPS" --rules "$RULES"[/green]
+        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUPS" --rules "$RULES"[/dim]
 
     - Create with custom ID, name, and description.
-        $ [green]RUN_GROUP='{{
+        $ [dim]RUN_GROUP='{{
             "id": "rg1",
             "instance_id": "inst-123"
         }}'
@@ -148,10 +147,10 @@ app = typer.Typer()
         nextmv cloud ensemble create --app-id hare-app \\
             --ensemble-definition-id prod-ensemble --name "Production Ensemble" \\
             --description "Production ensemble with multiple solvers" \\
-            --run-groups "$RUN_GROUP" --rules "$RULE"[/green]
+            --run-groups "$RUN_GROUP" --rules "$RULE"[/dim]
 
     - Create with run group repetitions.
-        $ [green]RUN_GROUP='{{
+        $ [dim]RUN_GROUP='{{
             "id": "rg1",
             "instance_id": "inst-123",
             "repetitions": 5
@@ -163,7 +162,7 @@ app = typer.Typer()
             "tolerance": {{"value": 0.1, "type": "relative"}},
             "index": 0
         }}'
-        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP" --rules "$RULE"[/green]
+        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP" --rules "$RULE"[/dim]
     """
 )
 def create(

nextmv/cli/cloud/ensemble/delete.py

@@ -5,9 +5,9 @@ This module defines the cloud ensemble delete command for the Nextmv CLI.
 from typing import Annotated
 
 import typer
-from rich.prompt import Confirm
 
 from nextmv.cli.configuration.config import build_app
+from nextmv.cli.confirm import get_confirmation
 from nextmv.cli.message import info, success
 from nextmv.cli.options import AppIDOption, EnsembleDefinitionIDOption, ProfileOption
 
@@ -32,24 +32,23 @@ def delete(
     """
     Deletes a Nextmv Cloud ensemble definition.
 
-    This action is permanent and cannot be undone. Use the [code]--yes[/code]
+    This action is permanent and cannot be undone. Use the --yes
     flag to skip the confirmation prompt.
 
     [bold][underline]Examples[/underline][/bold]
 
     - Delete the ensemble definition with the ID [magenta]prod-ensemble[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble[/green]
+        $ [dim]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble[/dim]
 
     - Delete the ensemble definition without confirmation prompt.
-        $ [green]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble --yes[/green]
+        $ [dim]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble --yes[/dim]
     """
 
     if not yes:
-        confirm = Confirm.ask(
+        confirm = get_confirmation(
             f"Are you sure you want to delete ensemble definition [magenta]{ensemble_definition_id}[/magenta] "
             f"from application [magenta]{app_id}[/magenta]? This action cannot be undone.",
-            default=False,
         )
 
         if not confirm:

nextmv/cli/cloud/ensemble/get.py

@@ -40,13 +40,13 @@ def get(
 
     - Get the ensemble definition with the ID [magenta]prod-ensemble[/magenta] from
       application [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud ensemble get --app-id hare-app \\
-        --ensemble-definition-id prod-ensemble[/green]
+        $ [dim]nextmv cloud ensemble get --app-id hare-app \\
+        --ensemble-definition-id prod-ensemble[/dim]
 
     - Get the ensemble definition with the ID [magenta]prod-ensemble[/magenta] and
       save the information to an [magenta]ensemble.json[/magenta] file.
-        $ [green]nextmv cloud ensemble get --app-id hare-app \\
-            --ensemble-definition-id prod-ensemble --output ensemble.json[/green]
+        $ [dim]nextmv cloud ensemble get --app-id hare-app \\
+            --ensemble-definition-id prod-ensemble --output ensemble.json[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/ensemble/list.py

@@ -0,0 +1,63 @@
+"""
+This module defines the cloud ensemble list command for the Nextmv CLI.
+"""
+
+import json
+from typing import Annotated
+
+import typer
+
+from nextmv.cli.configuration.config import build_app
+from nextmv.cli.message import in_progress, print_json, success
+from nextmv.cli.options import AppIDOption, ProfileOption
+
+# Set up subcommand application.
+app = typer.Typer()
+
+
+@app.command()
+def list(
+    app_id: AppIDOption,
+    output: Annotated[
+        str | None,
+        typer.Option(
+            "--output",
+            "-o",
+            help="Saves the list of ensemble definitions to this location.",
+            metavar="OUTPUT_PATH",
+        ),
+    ] = None,
+    profile: ProfileOption = None,
+) -> None:
+    """
+    List all Nextmv Cloud ensemble definitions for an application.
+
+    This command retrieves all ensemble definitions associated with the specified
+    application.
+
+    [bold][underline]Examples[/underline][/bold]
+
+    - List all ensemble definitions for application [magenta]hare-app[/magenta].
+        $ [dim]nextmv cloud ensemble list --app-id hare-app[/dim]
+
+    - List all ensemble definitions and save to a file.
+        $ [dim]nextmv cloud ensemble list --app-id hare-app --output ensembles.json[/dim]
+
+    - List all ensemble definitions using a specific profile.
+        $ [dim]nextmv cloud ensemble list --app-id hare-app --profile prod[/dim]
+    """
+
+    cloud_app = build_app(app_id=app_id, profile=profile)
+    in_progress(msg="Listing ensemble definitions...")
+    ensembles = cloud_app.list_ensemble_definitions()
+    ensembles_dict = [ensemble.to_dict() for ensemble in ensembles]
+
+    if output is not None and output != "":
+        with open(output, "w") as f:
+            json.dump(ensembles_dict, f, indent=2)
+
+        success(msg=f"Ensemble definitions list saved to [magenta]{output}[/magenta].")
+
+        return
+
+    print_json(ensembles_dict)