nextmv 1.0.0__py3-none-any.whl → 1.0.0.dev0__py3-none-any.whl

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,27 +33,31 @@ 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 --yes
+    associated data, including runs, will be deleted. Use the [code]--yes[/code]
     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].
-        $ [dim]nextmv cloud batch delete --app-id hare-app --batch-experiment-id hop-analysis[/dim]
+        $ [green]nextmv cloud batch delete --app-id hare-app --batch-experiment-id hop-analysis[/green]
 
     - Delete the batch experiment without confirmation prompt.
-        $ [dim]nextmv cloud batch delete --app-id hare-app --batch-experiment-id carrot-routes --yes[/dim]
+        $ [green]nextmv cloud batch delete --app-id hare-app --batch-experiment-id carrot-routes --yes[/green]
     """
 
     if not yes:
-        confirm = get_confirmation(
+        confirm = Confirm.ask(
             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:
-            info(f"Batch experiment [magenta]{batch_experiment_id}[/magenta] will not be deleted.")
+            info(
+                msg=f"Batch experiment [magenta]{batch_experiment_id}[/magenta] will not be deleted.",
+                emoji=":bulb:",
+            )
             return
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/batch/get.py

@@ -42,16 +42,16 @@ def get(
             "--wait",
             "-w",
             help="Wait for the batch experiment to complete. Results are printed to [magenta]stdout[/magenta]. "
-            "Specify output location with --output.",
+            "Specify output location with [code]--output[/code].",
         ),
     ] = False,
     profile: ProfileOption = None,
 ) -> None:
     """
-    Get a Nextmv Cloud batch experiment, including its runs.
+    Get a Nextmv Cloud batch experiment.
 
-    Use the --wait flag to wait for the batch experiment to
-    complete, polling for results. Using the --output flag will
+    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.
 
@@ -59,17 +59,17 @@ def get(
 
     - Get the batch experiment with ID [magenta]carrot-optimization[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id carrot-optimization[/dim]
+        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id carrot-optimization[/green]
 
     - Get the batch experiment and wait for it to complete if necessary.
-        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id bunny-hop-test --wait[/dim]
+        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id bunny-hop-test --wait[/green]
 
     - Get the batch experiment and save the results to a file.
-        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id warren-planning \\
-            --output results.json[/dim]
+        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id warren-planning \\
+            --output results.json[/green]
 
     - Get the batch experiment using a specific profile.
-        $ [dim]nextmv cloud batch get --app-id hare-app --batch-experiment-id lettuce-routes --profile prod[/dim]
+        $ [green]nextmv cloud batch get --app-id hare-app --batch-experiment-id lettuce-routes --profile prod[/green]
     """
 
     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].
-        $ [dim]nextmv cloud batch list --app-id hare-app[/dim]
+        $ [green]nextmv cloud batch list --app-id hare-app[/green]
 
     - List all batch experiments and save to a file.
-        $ [dim]nextmv cloud batch list --app-id hare-app --output experiments.json[/dim]
+        $ [green]nextmv cloud batch list --app-id hare-app --output experiments.json[/green]
 
     - List all batch experiments using a specific profile.
-        $ [dim]nextmv cloud batch list --app-id hare-app --profile prod[/dim]
+        $ [green]nextmv cloud batch list --app-id hare-app --profile prod[/green]
     """
 
     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].
-        $ [dim]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id bunny-warren-optimization[/dim]
+        $ [green]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id bunny-warren-optimization[/green]
 
     - Get metadata and save to a file.
-        $ [dim]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id lettuce-delivery \\
-            --output metadata.json[/dim]
+        $ [green]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id lettuce-delivery \\
+            --output metadata.json[/green]
 
     - Get metadata using a specific profile.
-        $ [dim]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id hop-schedule --profile prod[/dim]
+        $ [green]nextmv cloud batch metadata --app-id hare-app --batch-experiment-id hop-schedule --profile prod[/green]
     """
 
     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.
-        $ [dim]nextmv cloud batch update --app-id hare-app --batch-experiment-id carrot-feast \\
-            --name "Spring Carrot Harvest"[/dim]
+        $ [green]nextmv cloud batch update --app-id hare-app --batch-experiment-id carrot-feast \\
+            --name "Spring Carrot Harvest"[/green]
 
     - Update the description of a batch experiment.
-        $ [dim]nextmv cloud batch update --app-id hare-app --batch-experiment-id bunny-hop-routes \\
-            --description "Optimizing hop paths through the meadow"[/dim]
+        $ [green]nextmv cloud batch update --app-id hare-app --batch-experiment-id bunny-hop-routes \\
+            --description "Optimizing hop paths through the meadow"[/green]
 
     - Update both name and description and save the result.
-        $ [dim]nextmv cloud batch update --app-id hare-app --batch-experiment-id lettuce-delivery \\
+        $ [green]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[/dim]
+            --output updated-batch.json[/green]
     """
 
     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 components.
+    Upload data for Nextmv Cloud application runs.
 
     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 components.
+    Upload data for Nextmv Cloud application runs.
 
     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 --upload-url flag is required to specify the pre-signed
+    The [code]--upload-url[/code] 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
-    --input flag. When using the --input flag, the value can be one of the
-    following:
+    [code]--input[/code] flag. When using the [code]--input[/code] flag, the
+    value can be one of the following:
 
-    - [yellow]<FILE_PATH>[/yellow]: path to a [magenta]file[/magenta] containing
+    - [green]<FILE_PATH>[/green]: path to a [magenta]file[/magenta] containing
       the data. Use with the [magenta]json[/magenta], and
       [magenta]text[/magenta] content formats.
-    - [yellow]<DIR_PATH>[/yellow]: path to a [magenta]directory[/magenta]
+    - [green]<DIR_PATH>[/green]: path to a [magenta]directory[/magenta]
       containing data files. Use with the [magenta]multi-file[/magenta]
       content format.
-    - [yellow]<.tar.gz PATH>[/yellow]: path to a [magenta].tar.gz[/magenta] file
+    - [green]<.tar.gz_PATH>[/green]: 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].
-        $ [dim]echo '{"key": "value"}' | nextmv cloud data upload --app-id hare-app --upload-url <URL>[/dim]
+        $ [green]echo '{"key": "value"}' | nextmv cloud data upload --app-id hare-app --upload-url <URL>[/green]
 
     - Upload data from a [magenta]JSON[/magenta] file.
-        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json[/dim]
+        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json[/green]
 
     - Upload data from a [magenta]text[/magenta] file.
-        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.txt[/dim]
+        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.txt[/green]
 
     - Upload [magenta]multi-file[/magenta] data from a directory.
-        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input ./data_directory[/dim]
+        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input ./data_directory[/green]
 
     - Upload [magenta]multi-file[/magenta] data from a
       [magenta].tar.gz[/magenta] file.
-        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.tar.gz[/dim]
+        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.tar.gz[/green]
 
     - Upload data using a specific profile.
-        $ [dim]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json \\
-            --profile production[/dim]
+        $ [green]nextmv cloud data upload --app-id hare-app --upload-url <URL> --input data.json \\
+            --profile production[/green]
     """
 
     # 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 --input flag or [magenta]stdin[/magenta].")
+        error("Input data must be provided via the [code]--input[/code] 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,7 +7,6 @@ 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.
@@ -15,7 +14,6 @@ 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,12 +30,13 @@ app = typer.Typer()
     [bold][underline]Run Groups[/underline][/bold]
 
     Run groups are provided as [magenta]json[/magenta] objects using the
-    --run-groups flag. Each run group specifies how child runs are executed.
+    [code]--run-groups[/code] 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 --run-groups flag.
-    - Multiple run groups as a [magenta]json[/magenta] array in a single --run-groups flag.
+    - 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.
 
     Each run group must have the following fields:
     - [magenta]id[/magenta]: Unique identifier for the run group (required).
@@ -45,23 +46,23 @@ app = typer.Typer()
     - [magenta]repetitions[/magenta]: Number of times to repeat the run (optional).
 
     Object format:
-    [dim]{{
+    [green]{{
         "id": "rg1",
         "instance_id": "inst-123",
         "options": {{"param": "value"}},
         "repetitions": 5
-    }}[/dim]
+    }}[/green]
 
     [bold][underline]Evaluation Rules[/underline][/bold]
 
     Evaluation rules are provided as [magenta]json[/magenta] objects using the
-    --rules flag. Each rule determines how to evaluate and select the best
-    result from the child runs.
+    [code]--rules[/code] 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 --rules flag.
-    - Multiple rules as a [magenta]json[/magenta] array in a single --rules flag.
+    - Multiple rules by repeating the [code]--rules[/code] flag.
+    - Multiple rules as a [magenta]json[/magenta] array in a single [code]--rules[/code] flag.
 
     Each rule must have the following fields:
     - [magenta]id[/magenta]: Unique identifier for the rule (required).
@@ -74,18 +75,18 @@ app = typer.Typer()
     - [magenta]index[/magenta]: Evaluation order - lower indices evaluated first (required).
 
     Object format:
-    [dim]{{
+    [green]{{
         "id": "rule1",
         "statistics_path": "$.result.value",
         "objective": "minimize",
         "tolerance": {{"value": 0.1, "type": "relative"}},
         "index": 0
-    }}[/dim]
+    }}[/green]
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create an ensemble definition with a single run group and rule.
-        $ [dim]RUN_GROUP='{{
+        $ [green]RUN_GROUP='{{
             "id": "rg1",
             "instance_id": "inst-123"
         }}'
@@ -96,10 +97,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"[/dim]
+        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP" --rules "$RULE"[/green]
 
     - Create with multiple run groups by repeating the flag.
-        $ [dim]RUN_GROUP_1='{{
+        $ [green]RUN_GROUP_1='{{
             "id": "rg1",
             "instance_id": "inst-123"
         }}'
@@ -116,10 +117,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"[/dim]
+            --rules "$RULE"[/green]
 
     - Create with multiple items in a single JSON array.
-        $ [dim]RUN_GROUPS='[
+        $ [green]RUN_GROUPS='[
             {{"id": "rg1", "instance_id": "inst-123"}},
             {{"id": "rg2", "instance_id": "inst-456"}}
         ]'
@@ -130,10 +131,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"[/dim]
+        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUPS" --rules "$RULES"[/green]
 
     - Create with custom ID, name, and description.
-        $ [dim]RUN_GROUP='{{
+        $ [green]RUN_GROUP='{{
             "id": "rg1",
             "instance_id": "inst-123"
         }}'
@@ -147,10 +148,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"[/dim]
+            --run-groups "$RUN_GROUP" --rules "$RULE"[/green]
 
     - Create with run group repetitions.
-        $ [dim]RUN_GROUP='{{
+        $ [green]RUN_GROUP='{{
             "id": "rg1",
             "instance_id": "inst-123",
             "repetitions": 5
@@ -162,7 +163,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"[/dim]
+        nextmv cloud ensemble create --app-id hare-app --run-groups "$RUN_GROUP" --rules "$RULE"[/green]
     """
 )
 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,27 +32,31 @@ def delete(
     """
     Deletes a Nextmv Cloud ensemble definition.
 
-    This action is permanent and cannot be undone. Use the --yes
+    This action is permanent and cannot be undone. Use the [code]--yes[/code]
     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].
-        $ [dim]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble[/dim]
+        $ [green]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble[/green]
 
     - Delete the ensemble definition without confirmation prompt.
-        $ [dim]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble --yes[/dim]
+        $ [green]nextmv cloud ensemble delete --app-id hare-app --ensemble-definition-id prod-ensemble --yes[/green]
     """
 
     if not yes:
-        confirm = get_confirmation(
+        confirm = Confirm.ask(
             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:
-            info(f"Ensemble definition [magenta]{ensemble_definition_id}[/magenta] will not be deleted.")
+            info(
+                msg=f"Ensemble definition [magenta]{ensemble_definition_id}[/magenta] will not be deleted.",
+                emoji=":bulb:",
+            )
             return
 
     cloud_app = build_app(app_id=app_id, profile=profile)

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].
-        $ [dim]nextmv cloud ensemble get --app-id hare-app \\
-        --ensemble-definition-id prod-ensemble[/dim]
+        $ [green]nextmv cloud ensemble get --app-id hare-app \\
+        --ensemble-definition-id prod-ensemble[/green]
 
     - Get the ensemble definition with the ID [magenta]prod-ensemble[/magenta] and
       save the information to an [magenta]ensemble.json[/magenta] file.
-        $ [dim]nextmv cloud ensemble get --app-id hare-app \\
-            --ensemble-definition-id prod-ensemble --output ensemble.json[/dim]
+        $ [green]nextmv cloud ensemble get --app-id hare-app \\
+            --ensemble-definition-id prod-ensemble --output ensemble.json[/green]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/ensemble/update.py

@@ -58,27 +58,27 @@ def update(
     [bold][underline]Examples[/underline][/bold]
 
     - Update the name of an ensemble definition.
-        $ [dim]nextmv cloud ensemble update --app-id hare-app \\
-            --ensemble-definition-id prod-ensemble --name "Updated Production Ensemble"[/dim]
+        $ [green]nextmv cloud ensemble update --app-id hare-app \\
+            --ensemble-definition-id prod-ensemble --name "Updated Production Ensemble"[/green]
 
     - Update the description of an ensemble definition.
-        $ [dim]nextmv cloud ensemble update --app-id hare-app \\
+        $ [green]nextmv cloud ensemble update --app-id hare-app \\
             --ensemble-definition-id prod-ensemble \\
-            --description "Updated ensemble for production workloads"[/dim]
+            --description "Updated ensemble for production workloads"[/green]
 
     - Update both name and description.
-        $ [dim]nextmv cloud ensemble update --app-id hare-app \\
+        $ [green]nextmv cloud ensemble update --app-id hare-app \\
             --ensemble-definition-id prod-ensemble --name "Production Ensemble v2" \\
-            --description "Enhanced ensemble configuration for production"[/dim]
+            --description "Enhanced ensemble configuration for production"[/green]
 
     - Update and save the result to a file.
-        $ [dim]nextmv cloud ensemble update --app-id hare-app \\
+        $ [green]nextmv cloud ensemble update --app-id hare-app \\
             --ensemble-definition-id prod-ensemble --name "New Name" \\
-            --description "New Description" --output updated.json[/dim]
+            --description "New Description" --output updated.json[/green]
     """
 
     if name is None and description is None:
-        error("Provide at least one option to update: --name or --description.")
+        error("Provide at least one option to update: [code]--name[/code] or [code]--description[/code].")
 
     cloud_app = build_app(app_id=app_id, profile=profile)
 

nextmv/cli/cloud/input_set/__init__.py

@@ -5,7 +5,6 @@ This module defines the cloud input-set command tree for the Nextmv CLI.
 import typer
 
 from nextmv.cli.cloud.input_set.create import app as create_app
-from nextmv.cli.cloud.input_set.delete import app as delete_app
 from nextmv.cli.cloud.input_set.get import app as get_app
 from nextmv.cli.cloud.input_set.list import app as list_app
 from nextmv.cli.cloud.input_set.update import app as update_app
@@ -13,7 +12,6 @@ from nextmv.cli.cloud.input_set.update import app as update_app
 # Set up subcommand application.
 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/input_set/create.py

@@ -72,8 +72,7 @@ def create(
         typer.Option(
             "--start-time",
             formats=["%Y-%m-%dT%H:%M:%S%z"],
-            help="Start time for filtering runs in [magenta]RFC 3339[/magenta] format. "
-            "Object format: [dim]'2024-01-01T00:00:00Z'[/dim]",
+            help="Start time for filtering runs. (example: [magenta]'2024-01-01T00:00:00Z'[/magenta])",
             metavar="START_TIME",
         ),
     ] = None,
@@ -82,8 +81,7 @@ def create(
         typer.Option(
             "--end-time",
             formats=["%Y-%m-%dT%H:%M:%S%z"],
-            help="End time for filtering runs in [magenta]RFC 3339[/magenta] format. "
-            "Object format: [dim]'2024-01-01T00:00:00Z'[/dim]",
+            help="End time for filtering runs. (example: [magenta]'2024-01-01T00:00:00Z'[/magenta])",
             metavar="END_TIME",
         ),
     ] = None,
@@ -96,13 +94,13 @@ def create(
             metavar="MAXIMUM_RUNS",
         ),
     ] = 20,
-    managed_inputs: Annotated[
+    inputs: Annotated[
         str | None,
         typer.Option(
-            "--managed-inputs",
-            help="Managed inputs for the input set. Data should be valid [magenta]json[/magenta]. Object "
-            "format: [dim][{'id': 'id', 'name': 'name', 'description': 'description'}][/dim].",
-            metavar="MANAGED_INPUTS",
+            "--inputs",
+            help="Inputs for the input set. Data should be valid [magenta]json[/magenta]. Object "
+            "format: [magenta][{'id': 'id', 'name': 'name', 'description': 'description'}][/magenta].",
+            metavar="INPUTS",
         ),
     ] = None,
     profile: ProfileOption = None,
@@ -113,30 +111,32 @@ def create(
     An input set is a collection of inputs that can be reused across multiple
     experiments.
 
-    1. --run-ids: Create from a list of existing run IDs.
-    2. --managed-inputs: Create from existing managed inputs in the application.
-    3. --instance-id with --start-time and --end-time:
+    1. [code]--run-ids[/code]: Create from a list of existing run IDs.
+
+    2. [code]--inputs[/code]: Create from existing managed inputs in the application.
+
+    3. [code]--instance-id[/code] with [code]--start-time[/code] and [code]--end-time[/code]:
        Create from instance runs matching the time range criteria.
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create an input set for application [magenta]hare-app[/magenta] from runs.
       A random input set ID will be generated if one is not provided.
-        $ [dim]nextmv cloud input-set create --app-id hare-app \\
-            --name "Hare Input Set" --run-ids run-1 --run-ids run-2 --run-ids run-3"[/dim]
+        $ [green]nextmv cloud input-set create --app-id hare-app \\
+            --name "Hare Input Set" --run-ids run-1 --run-ids run-2 --run-ids run-3"[/green]
 
     - Create an input set with a specific ID.
-        $ [dim]nextmv cloud input-set create --app-id hare-app --input-set-id hare-input-set \\
-            --name "Hare Input Set" --run-ids run-1 --run-ids run-2 --run-ids run-3"[/dim]
+        $ [green]nextmv cloud input-set create --app-id hare-app --input-set-id hare-input-set \\
+            --name "Hare Input Set" --run-ids run-1 --run-ids run-2 --run-ids run-3"[/green]
 
     - Create an input set using existing managed inputs.
-        $ [dim]nextmv cloud input-set create --app-id hare-app --name "Hare Input Set" \\
-            --managed-inputs '[{"id": "hare-input-1", "name": "hare input", "description": "hare description"}]'[/dim]
+        $ [green]nextmv cloud input-set create --app-id hare-app --name "Hare Input Set" \\
+            --inputs '[{"id": "hare-input-1", "name": "hare input", "description": "hare description"}]'[/green]
 
     - Create an input set from runs using a specific instance and time range.
-        $ [dim]nextmv cloud input-set create --app-id hare-app --name "Hare Input Set" \\
+        $ [green]nextmv cloud input-set create --app-id hare-app --name "Hare Input Set" \\
             --instance-id hare-instance --start-time "2024-01-01T00:00:00Z" \\
-            --end-time "2024-01-31T23:59:59Z"[/dim]
+            --end-time "2024-01-31T23:59:59Z"[/green]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)
@@ -147,8 +147,8 @@ def create(
         input_set_id = safe_id("input-set")
 
     managed_inputs = []
-    if managed_inputs is not None:
-        for d in json.loads(managed_inputs):
+    if inputs is not None:
+        for d in json.loads(inputs):
             i = ManagedInput.from_dict(d)
             if i is None:
                 error(f"[magenta]{d}[/magenta] is not a valid [yellow]ManagedInput[/yellow]")

nextmv/cli/cloud/input_set/get.py

@@ -39,12 +39,12 @@ def get(
     [bold][underline]Examples[/underline][/bold]
 
     - Get an input set with the ID [magenta]hare-input-set[/magenta].
-        $ [dim]nextmv cloud input-set get --app-id hare-app --input-set-id hare-input-set[/dim]
+        $ [green]nextmv cloud input-set get --app-id hare-app --input-set-id hare-input-set[/green]
 
     - Get an input set with the ID [magenta]hare-input-set[/magenta] and save
       the information to a [magenta]input-set.json[/magenta] file.
-        $ [dim]nextmv cloud input-set get --app-id hare-app --input-set-id hare-input-set \\
-            --output input-set.json[/dim]
+        $ [green]nextmv cloud input-set get --app-id hare-app --input-set-id hare-input-set \\
+            --output input-set.json[/green]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

nextmv/cli/cloud/input_set/list.py

@@ -38,13 +38,13 @@ def list(
     [bold][underline]Examples[/underline][/bold]
 
     - List all input sets of application [magenta]hare-app[/magenta].
-        $ [dim]nextmv cloud input-set list --app-id hare-app[/dim]
+        $ [green]nextmv cloud input-set list --app-id hare-app[/green]
 
     - List all input sets using the profile named [magenta]hare[/magenta].
-        $ [dim]nextmv cloud input-set list --app-id hare-app --profile hare[/dim]
+        $ [green]nextmv cloud input-set list --app-id hare-app --profile hare[/green]
 
     - List all input sets and save the information to a [magenta]input-sets.json[/magenta] file.
-        $ [dim]nextmv cloud input-set list --app-id hare-app --output input-sets.json[/dim]
+        $ [green]nextmv cloud input-set list --app-id hare-app --output input-sets.json[/green]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)