nextmv 1.0.0.dev3__tar.gz → 1.0.0.dev5__tar.gz

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nextmv
-Version: 1.0.0.dev3
+Version: 1.0.0.dev5
 Summary: The all-purpose Python SDK for Nextmv
 Project-URL: Homepage, https://www.nextmv.io
 Project-URL: Documentation, https://nextmv-py.docs.nextmv.io/en/latest/nextmv/

nextmv-1.0.0.dev5/nextmv/__about__.py

@@ -0,0 +1 @@
+__version__ = "v1.0.0.dev5"

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/__entrypoint__.py

@@ -10,13 +10,12 @@ human to use it during local development. It is the standard way in which a
 from mlflow.pyfunc import load_model
 
 import nextmv
-from nextmv import cloud
 
 
 def main() -> None:
     """Entry point for the program."""
 
-    manifest = cloud.Manifest.from_yaml(".")
+    manifest = nextmv.Manifest.from_yaml(".")
 
     # Load the options from the manifest.
     options = manifest.extract_options()

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/__init__.py

@@ -11,7 +11,6 @@ from .input import LocalInputLoader as LocalInputLoader
 from .input import csv_data_file as csv_data_file
 from .input import json_data_file as json_data_file
 from .input import load as load
-from .input import load_local as load_local
 from .input import text_data_file as text_data_file
 from .logger import log as log
 from .logger import redirect_stdout as redirect_stdout
@@ -31,7 +30,6 @@ from .model import Model as Model
 from .model import ModelConfiguration as ModelConfiguration
 from .options import Option as Option
 from .options import Options as Options
-from .options import Parameter as Parameter
 from .output import Asset as Asset
 from .output import DataPoint as DataPoint
 from .output import LocalOutputWriter as LocalOutputWriter
@@ -50,7 +48,6 @@ from .output import csv_solution_file as csv_solution_file
 from .output import json_solution_file as json_solution_file
 from .output import text_solution_file as text_solution_file
 from .output import write as write
-from .output import write_local as write_local
 from .polling import DEFAULT_POLLING_OPTIONS as DEFAULT_POLLING_OPTIONS
 from .polling import PollingOptions as PollingOptions
 from .polling import default_polling_options as default_polling_options
@@ -79,7 +76,6 @@ from .run import TrackedRunStatus as TrackedRunStatus
 from .run import run_duration as run_duration
 from .safe import safe_id as safe_id
 from .safe import safe_name_and_id as safe_name_and_id
-from .status import Status as Status
 from .status import StatusV2 as StatusV2
 
 VERSION = __version__

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/_serialization.py

@@ -90,7 +90,7 @@ def _custom_serial(obj: Any) -> str:
         If the object type is not supported for serialization.
     """
 
-    if isinstance(obj, (datetime.datetime, datetime.date)):
+    if isinstance(obj, datetime.datetime | datetime.date):
         return obj.isoformat()
 
     raise TypeError(f"Type {type(obj)} not serializable")

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/CONTRIBUTING.md

@@ -173,23 +173,26 @@ guidelines:
 
 ## Confirmation prompts
 
-For destructive actions (like deletions), use `rich.prompt.Confirm.ask()` to
-ask for user confirmation before proceeding. Follow these guidelines:
+For destructive actions (like deletions), use the `get_confirmation()` method
+to ask for user confirmation before proceeding. The method is available from
+the `cli/confirm.py` file. This method already handles sensible values used for
+getting a confirmation from a user. Additionally, it handles non-interactive
+sessions by defaulting to `False` if no input can be provided.
 
-- The confirmation message should use `[magenta]` for the variable being
+When using confirmation prompts, follow these guidelines:
+
+- The confirmation message should use `[magenta]` for the variable/s being
   affected.
-- Set `default=False` for safety, so the user must explicitly confirm.
-- Provide a `--yes` / `-y` flag to skip the confirmation prompt, useful for
-  non-interactive sessions.
+- Provide a `--yes` / `-y` flag to skip the confirmation prompt where possible,
+  useful for non-interactive sessions.
 - If the user declines, call `info()` with the `:bulb:` emoji and return early.
 
 Consider the `nextmv cloud app delete` command:
 
 ```python
 if not yes:
-    confirm = Confirm.ask(
-        f"Are you sure you want to delete application [magenta]{app_id}[/magenta]? This action cannot be undone",
-        default=False,
+    confirm = get_confirmation(
+        f"Are you sure you want to delete application [magenta]{app_id}[/magenta]? This action cannot be undone.",
     )
 
     if not confirm:
@@ -197,14 +200,63 @@ if not yes:
         return
 ```
 
-## Formatting
+## Formatting, colors, and styles
+
+Use these Rich markup colors/styles when formatting help text and messages.
+These are the main colors/styles that can be used for highlighting/contrast (we
+limit colors to keep coloring consistent):
+
+- `[code]`: commands. CLI related variables. - technical things that are CLI
+  commands.
+- `[magenta]`: variable names, values, literals, etc. - mainly short technical things.
+- `[dim]`: examples. - longer technical things.
+- `[yellow]`: emphasis, highlight of special items, type contrast to
+  `[magenta]`. Use sparingly only.
 
-Use these Rich markup guidelines when formatting help text and messages.
+In any case, the best advice is to follow existing examples in the codebase to
+maintain consistency.
 
-- When talking about a command, or a command option, use the `[code]` `[/code]`
-  tags. Take this example from the help menu of the `cloud/app/delete.py` file.
-  In the command help, when referring to the `--yes` option, we use
-  `[code]--yes[/code]` to format it as code.
+Here are some guidelines for when to use each formatting style.
+
+- When talking about a command use the `[code]` `[/code]` tags. Consider the
+  help message of the `cloud/shadow/stop.py` file. We tell the user they can
+  delete an experiment with the `nextmv cloud shadow delete` command. The
+  formatting of that command is done using the `[code]` `[/code]` tags:
+
+  ```python
+  @app.command()
+  def stop(
+      app_id: AppIDOption,
+      shadow_test_id: ShadowTestIDOption,
+      profile: ProfileOption = None,
+  ) -> None:
+      """
+      Stops a Nextmv Cloud shadow test.
+
+      Before stopping a shadow test, it must be in a started state. Experiments
+      in a [magenta]draft[/magenta] state, that haven't started, can be deleted
+      with the [code]nextmv cloud shadow delete[/code] command.
+
+      [bold][underline]Examples[/underline][/bold]
+
+      - Stop the shadow test with the ID [magenta]hop-analysis[/magenta] from application
+        [magenta]hare-app[/magenta].
+          $ [dim]nextmv cloud shadow stop --app-id hare-app --shadow-test-id hop-analysis[/dim]
+      """
+
+      in_progress(msg="Stopping shadow test...")
+      cloud_app = build_app(app_id=app_id, profile=profile)
+      cloud_app.stop_shadow_test(shadow_test_id=shadow_test_id)
+      success(
+          f"Shadow test [magenta]{shadow_test_id}[/magenta] stopped successfully "
+          f"in application [magenta]{app_id}[/magenta]."
+      )
+  ```
+
+- When talking about a command option, there is no formatting needed. Typer
+  automatically adds coloring to options in the help menu. Take this example
+  from the help menu of the `cloud/app/delete.py` file. In the command help,
+  when referring to the `--yes` option:
 
   ```python
   @app.command()
@@ -223,16 +275,16 @@ Use these Rich markup guidelines when formatting help text and messages.
       """
       Deletes a Nextmv Cloud application.
 
-      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 application with the ID [magenta]hare-app[/magenta].
-          $ [green]nextmv cloud app delete --app-id hare-app[/green]
+          $ [dim]nextmv cloud app delete --app-id hare-app[/dim]
 
       - Delete the application with the ID [magenta]hare-app[/magenta] without confirmation prompt.
-          $ [green]nextmv cloud app delete --app-id hare-app --yes[/green]
+          $ [dim]nextmv cloud app delete --app-id hare-app --yes[/dim]
       """
   ```
 
@@ -246,6 +298,12 @@ Use these Rich markup guidelines when formatting help text and messages.
   error(f"Input path [magenta]{input}[/magenta] does not exist.")
   ```
 
+- When talking about longer technical things, like examples for a command
+  usage, or examples of a JSON object, use the `[dim]` `[/dim]` tags. Consider
+  the examples section of the `cloud/app/delete.py` file above. The example
+  commands are formatted using the `[dim]` `[/dim]` tags. The `[dim]` tag is
+  discussed in more detail in the command documentation section below.
+
 - Links to URLs should be formatted using the `[link=URL_LINK][bold]
   [/bold][/link]` tags. Consider the main help message of the `nextmv
   community` command, in the `community/__init__.py` file:
@@ -265,11 +323,6 @@ Use these Rich markup guidelines when formatting help text and messages.
   The link provided is <https://github.com/nextmv-io/community-apps>, and it will
   be applied to the text `nextmv-io/community-apps`.
 
-- Colors that can be used for highlighting (we limit colors to keep coloring consistent):
-  - `[magenta]`: variable, literals, etc. - mainly short technical things (see above).
-  - `[green]`: commands, etc. - longer technical things, or, as a type-contrast to magenta.
-  - `[yellow]`: emphasis, highlight of special items, etc. (use sparingly only).
-
 ## Command documentation
 
 Every command should have good-enough documentation that guides the user on how
@@ -316,11 +369,11 @@ to use it.
       [bold][underline]Examples[/underline][/bold]
 
       - Get the application with the ID [magenta]hare-app[/magenta].
-          $ [green]nextmv cloud app get --app-id hare-app[/green]
+          $ [dim]nextmv cloud app get --app-id hare-app[/dim]
 
       - Get the application with the ID [magenta]hare-app[/magenta] and save the information to an
         [magenta]app.json[/magenta] file.
-          $ [green]nextmv cloud app get --app-id hare-app --output app.json[/green]
+          $ [dim]nextmv cloud app get --app-id hare-app --output app.json[/dim]
       """
 
       client = build_client(profile)
@@ -353,11 +406,10 @@ to use it.
 
   - The examples section is fenced with the `[bold][underline]
     [/underline][/bold]` tags.
-
   - Each example is listed as a bullet, using a hyphen (`-`).
   - Each example has a short description, followed by the command itself in a
     new line, with 4 spaces of indentation in comparison to where the hyphen is.
-  - The command itself should be formatted using the `[green]` `[/green]` tags.
+  - The command itself should be formatted using the `[dim]` `[/dim]` tags.
   - The command should start with a dollar sign (`$`), followed by a space, and
     then the actual command.
   - When an example command is too long, use a double backslash (`\\`) for line
@@ -366,8 +418,8 @@ to use it.
 
     ```text
     - Create an application with an ID and description.
-        $ [green]nextmv cloud app create --name "Hare App" --app-id hare-app \\
-            --description "An application for routing hares"[/green]
+        $ [dim]nextmv cloud app create --name "Hare App" --app-id hare-app \\
+            --description "An application for routing hares"[/dim]
     ```
 
 ## Command options

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/acceptance/create.py

@@ -27,27 +27,25 @@ app = typer.Typer()
 
     The acceptance test is based on a batch experiment. If the batch experiment
     with the same ID already exists, it will be reused. Otherwise, you must
-    provide the [code]--input-set-id[/code] option to create a new batch
-    experiment.
+    provide the --input-set-id option to create a new batch experiment.
 
-    Use the [code]--wait[/code] flag to wait for the acceptance test 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 acceptance test 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]Metrics[/underline][/bold]
 
     Metrics are provided as [magenta]json[/magenta] objects using the
-    [code]--metrics[/code] flag. Each metric defines how to compare the
+    --metrics flag. Each metric defines how to compare the
     candidate and baseline instances.
 
     You can provide metrics in three ways:
     - A single metric as a [magenta]json[/magenta] object.
-    - Multiple metrics by repeating the [code]--metrics[/code] flag.
-    - Multiple metrics as a [magenta]json[/magenta] array in a single [code]--metrics[/code] flag.
+    - Multiple metrics by repeating the --metrics flag.
+    - Multiple metrics as a [magenta]json[/magenta] array in a single --metrics flag.
 
     Each metric must have the following fields:
-    - [magenta]field[/magenta]: Field of the metric to measure (e.g., "solution.objective").
+    - [magenta]field[/magenta]: Field of the metric to measure (e.g., "result.custom.unassigned").
     - [magenta]metric_type[/magenta]: Type of metric comparison. Allowed values: {enum_values(MetricType)}.
     - [magenta]params[/magenta]: Parameters of the metric comparison.
         - [magenta]operator[/magenta]: Comparison operator. Allowed values: {enum_values(Comparison)}.
@@ -57,7 +55,7 @@ app = typer.Typer()
     - [magenta]statistic[/magenta]: Statistical method. Allowed values: {enum_values(StatisticType)}.
 
     Object format:
-    [green]{{
+    [dim]{{
         "field": "field",
         "metric_type": "type",
         "params": {{
@@ -68,13 +66,13 @@ app = typer.Typer()
             }}
         }},
         "statistic": "statistic"
-    }}[/green]
+    }}[/dim]
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create an acceptance test with a single metric.
         $ [green]METRIC='{{
-            "field": "solution.objective",
+            "field": "result.custom.unassigned",
             "metric_type": "direct-comparison",
             "params": {{
                 "operator": "lt",
@@ -84,11 +82,11 @@ app = typer.Typer()
         }}'
         nextmv cloud acceptance create --app-id hare-app --acceptance-test-id test-123 \\
             --candidate-instance-id candidate-123 --baseline-instance-id baseline-456 \\
-            --metrics "$METRIC" --input-set-id input-set-123[/green]
+            --metrics "$METRIC" --input-set-id input-set-123[/dim]
 
     - Create with multiple metrics by repeating the flag.
         $ [green]METRIC1='{{
-            "field": "solution.objective",
+            "field": "result.custom.unassigned",
             "metric_type": "direct-comparison",
             "params": {{
                 "operator": "lt",
@@ -97,7 +95,7 @@ app = typer.Typer()
             "statistic": "mean"
         }}'
         METRIC2='{{
-            "field": "statistics.run.duration",
+            "field": "run.duration",
             "metric_type": "direct-comparison",
             "params": {{
                 "operator": "le",
@@ -107,12 +105,12 @@ app = typer.Typer()
         }}'
         nextmv cloud acceptance create --app-id hare-app --acceptance-test-id test-123 \\
             --candidate-instance-id candidate-123 --baseline-instance-id baseline-456 \\
-            --metrics "$METRIC1" --metrics "$METRIC2" --input-set-id input-set-123[/green]
+            --metrics "$METRIC1" --metrics "$METRIC2" --input-set-id input-set-123[/dim]
 
     - Create with multiple metrics in a single [magenta]json[/magenta] array.
-        $ [green]METRICS='[
+        $ [dim]METRICS='[
             {{
-                "field": "solution.objective",
+                "field": "result.custom.unassigned",
                 "metric_type": "direct-comparison",
                 "params": {{
                     "operator": "lt",
@@ -121,7 +119,7 @@ app = typer.Typer()
                 "statistic": "mean"
             }},
             {{
-                "field": "statistics.run.duration",
+                "field": "run.duration",
                 "metric_type": "direct-comparison",
                 "params": {{
                     "operator": "le",
@@ -132,11 +130,11 @@ app = typer.Typer()
         ]'
         nextmv cloud acceptance create --app-id hare-app --acceptance-test-id test-123 \\
             --candidate-instance-id candidate-123 --baseline-instance-id baseline-456 \\
-            --metrics "$METRICS" --input-set-id input-set-123[/green]
+            --metrics "$METRICS" --input-set-id input-set-123[/dim]
 
     - Create an acceptance test and wait for it to complete.
         $ [green]METRIC='{{
-            "field": "solution.objective",
+            "field": "result.custom.unassigned",
             "metric_type": "direct-comparison",
             "params": {{
                 "operator": "lt",
@@ -146,11 +144,11 @@ app = typer.Typer()
         }}'
         nextmv cloud acceptance create --app-id hare-app --acceptance-test-id test-123 \\
             --candidate-instance-id candidate-123 --baseline-instance-id baseline-456 \\
-            --metrics "$METRIC" --input-set-id input-set-123 --wait[/green]
+            --metrics "$METRIC" --input-set-id input-set-123 --wait[/dim]
 
     - Create an acceptance test and save the results to a file, waiting for completion.
         $ [green]METRIC='{{
-            "field": "solution.objective",
+            "field": "result.custom.unassigned",
             "metric_type": "direct-comparison",
             "params": {{
                 "operator": "lt",
@@ -160,7 +158,7 @@ app = typer.Typer()
         }}'
         nextmv cloud acceptance create --app-id hare-app --acceptance-test-id test-123 \\
             --candidate-instance-id candidate-123 --baseline-instance-id baseline-456 \\
-            --metrics "$METRIC" --input-set-id input-set-123 --output results.json[/green]
+            --metrics "$METRIC" --input-set-id input-set-123 --output results.json[/dim]
     """
 )
 def create(
@@ -265,7 +263,7 @@ def create(
             "--wait",
             "-w",
             help="Wait for the acceptance test 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,

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/acceptance/delete.py

@@ -5,9 +5,9 @@ This module defines the cloud acceptance 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 AcceptanceTestIDOption, AppIDOption, ProfileOption
 
@@ -32,25 +32,24 @@ def delete(
     """
     Deletes a Nextmv Cloud acceptance test.
 
-    This action is permanent and cannot be undone. The underlying batch experiment
-    and associated data will also be deleted. Use the [code]--yes[/code] flag to skip
-    the confirmation prompt.
+    This action is permanent and cannot be undone. The underlying batch
+    experiment and associated data will also be deleted. Use the --yes flag to
+    skip the confirmation prompt.
 
     [bold][underline]Examples[/underline][/bold]
 
     - Delete the acceptance test with the ID [magenta]test-cotton-tail[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail[/green]
+        $ [dim]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail[/dim]
 
     - Delete the acceptance test without confirmation prompt.
-        $ [green]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail --yes[/green]
+        $ [dim]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail --yes[/dim]
     """
 
     if not yes:
-        confirm = Confirm.ask(
+        confirm = get_confirmation(
             f"Are you sure you want to delete acceptance test [magenta]{acceptance_test_id}[/magenta] "
             f"from application [magenta]{app_id}[/magenta]? This action cannot be undone.",
-            default=False,
         )
 
         if not confirm:

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/acceptance/get.py

@@ -42,7 +42,7 @@ def get(
             "--wait",
             "-w",
             help="Wait for the acceptance test 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,26 +50,25 @@ def get(
     """
     Get a Nextmv Cloud acceptance test.
 
-    Use the [code]--wait[/code] flag to wait for the acceptance test 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 acceptance test 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]Examples[/underline][/bold]
 
     - Get the acceptance test with ID [magenta]test-123[/magenta] from application
       [magenta]hare-app[/magenta].
-        $ [green]nextmv cloud acceptance get --app-id hare-app --acceptance-test-id test-123[/green]
+        $ [dim]nextmv cloud acceptance get --app-id hare-app --acceptance-test-id test-123[/dim]
 
     - Get the acceptance test and wait for it to complete if necessary.
-        $ [green]nextmv cloud acceptance get --app-id hare-app --acceptance-test-id test-123 --wait[/green]
+        $ [dim]nextmv cloud acceptance get --app-id hare-app --acceptance-test-id test-123 --wait[/dim]
 
     - Get the acceptance test and save the results to a file.
-        $ [green]nextmv cloud acceptance get --app-id hare-app \\
-            --acceptance-test-id test-123 --output results.json[/green]
+        $ [dim]nextmv cloud acceptance get --app-id hare-app \\
+            --acceptance-test-id test-123 --output results.json[/dim]
 
     - Get the acceptance test using a specific profile.
-        $ [green]nextmv cloud acceptance get --app-id hare-app --acceptance-test-id test-123 --profile prod[/green]
+        $ [dim]nextmv cloud acceptance get --app-id hare-app --acceptance-test-id test-123 --profile prod[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/acceptance/list.py

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

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/acceptance/update.py

@@ -57,17 +57,17 @@ def update(
     [bold][underline]Examples[/underline][/bold]
 
     - Update the name of an acceptance test.
-        $ [green]nextmv cloud acceptance update --app-id hare-app \\
-            --acceptance-test-id test-123 --name "Updated Test Name"[/green]
+        $ [dim]nextmv cloud acceptance update --app-id hare-app \\
+            --acceptance-test-id test-123 --name "Updated Test Name"[/dim]
 
     - Update the description of an acceptance test.
-        $ [green]nextmv cloud acceptance update --app-id hare-app \\
-            --acceptance-test-id test-123 --description "Updated description"[/green]
+        $ [dim]nextmv cloud acceptance update --app-id hare-app \\
+            --acceptance-test-id test-123 --description "Updated description"[/dim]
 
     - Update both name and description and save the result.
-        $ [green]nextmv cloud acceptance update --app-id hare-app \\
+        $ [dim]nextmv cloud acceptance update --app-id hare-app \\
             --acceptance-test-id test-123 --name "New Name" \\
-            --description "New description" --output updated-test.json[/green]
+            --description "New description" --output updated-test.json[/dim]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/account/__init__.py

@@ -20,9 +20,9 @@ app.add_typer(update_app)
 @app.callback()
 def callback() -> None:
     """
-    Manage your Nextmv Cloud account (organization).
+    Manage SSO for your Nextmv Cloud account (organization).
 
-    Please contact [link=https://www.nextmv.io/contact][bold]Nextmv support[/bold][/link] for assistance
-    configuring SSO for your organization.
+    Please contact [link=https://www.nextmv.io/contact][bold]Nextmv support[/bold][/link]
+    for assistance configuring SSO for your organization.
     """
     pass

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/account/create.py

@@ -39,32 +39,32 @@ def create(
     profile: ProfileOption = None,
 ) -> None:
     """
-    Create a new Nextmv Cloud account.
+    Create a new Nextmv Cloud account in your organization.
 
     To create managed accounts, SSO must be configured for your organization.
     Please contact [link=https://www.nextmv.io/contact][bold]Nextmv support[/bold][/link] for assistance.
 
     At least one administrator email address must be provided. Multiple
-    administrators can be specified by repeating the [code]--admins[/code] flag
-    or by separating email addresses with commas.
+    administrators can be specified by repeating the --admins flag or by
+    separating email addresses with commas.
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create an account named [magenta]Bunny Logistics[/magenta] with a single administrator.
-        $ [green]nextmv cloud account create --name "Bunny Logistics" \\
-            --admins peter.rabbit@carrotexpress.com[/green]
+        $ [dim]nextmv cloud account create --name "Bunny Logistics" \\
+            --admins peter.rabbit@carrotexpress.com[/dim]
 
     - Create an account named [magenta]Hare Delivery Co[/magenta] with multiple administrators.
-        $ [green]nextmv cloud account create --name "Hare Delivery Co" \\
-            --admins bugs@acme.com --admins roger@toontown.com[/green]
+        $ [dim]nextmv cloud account create --name "Hare Delivery Co" \\
+            --admins bugs@acme.com --admins roger@toontown.com[/dim]
 
     - Create an account using the profile named [magenta]hare[/magenta].
-        $ [green]nextmv cloud account create --name "Cottontail Couriers" \\
-            --admins fluffy@hopmail.com --profile hare[/green]
+        $ [dim]nextmv cloud account create --name "Cottontail Couriers" \\
+            --admins fluffy@hopmail.com --profile hare[/dim]
 
     - Create an account with comma-separated administrators.
-        $ [green]nextmv cloud account create --name "Whiskers Warehouse" \\
-            --admins "thumper@forestmail.com,flopsy@warren.io"[/green]
+        $ [dim]nextmv cloud account create --name "Whiskers Warehouse" \\
+            --admins "thumper@forestmail.com,flopsy@warren.io"[/dim]
     """
 
     cloud_client = build_client(profile)

{nextmv-1.0.0.dev3 → nextmv-1.0.0.dev5}/nextmv/cli/cloud/account/delete.py

@@ -5,9 +5,9 @@ This module defines the cloud account delete command for the Nextmv CLI.
 from typing import Annotated
 
 import typer
-from rich.prompt import Confirm
 
 from nextmv.cli.configuration.config import build_account
+from nextmv.cli.confirm import get_confirmation
 from nextmv.cli.message import info, success
 from nextmv.cli.options import AccountIDOption, ProfileOption
 
@@ -29,26 +29,25 @@ def delete(
     profile: ProfileOption = None,
 ) -> None:
     """
-    Deletes an account within your organization.
+    Deletes an account within your SSO-enabled organization.
 
     You must have the [magenta]administrator[/magenta] role on that account in order to delete it.
 
-    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 account with the ID [magenta]bunnies-account[/magenta].
-        $ [green]nextmv cloud account delete --account-id bunnies-account[/green]
+        $ [dim]nextmv cloud account delete --account-id bunnies-account[/dim]
 
     - Delete the account without confirmation prompt.
-        $ [green]nextmv cloud account delete --account-id bunnies-account --yes[/green]
+        $ [dim]nextmv cloud account delete --account-id bunnies-account --yes[/dim]
     """
 
     if not yes:
-        confirm = Confirm.ask(
+        confirm = get_confirmation(
             f"Are you sure you want to delete account [magenta]{account_id}[/magenta]? This action cannot be undone.",
-            default=False,
         )
 
         if not confirm: