nextmv 1.0.0__tar.gz → 1.0.0.dev1__tar.gz

{nextmv-1.0.0 → nextmv-1.0.0.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: nextmv
-Version: 1.0.0
+Version: 1.0.0.dev1
 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/
@@ -229,20 +229,19 @@ Requires-Dist: plotly>=6.0.1; extra == 'all'
 Provides-Extra: dev
 Requires-Dist: build>=1.0.3; extra == 'dev'
 Requires-Dist: folium>=0.20.0; extra == 'dev'
-Requires-Dist: mlflow>=3.9.0; extra == 'dev'
-Requires-Dist: nextpipe>=0.6.0; extra == 'dev'
+Requires-Dist: mlflow>=2.19.0; extra == 'dev'
+Requires-Dist: nextroute>=1.11.1; extra == 'dev'
 Requires-Dist: openpyxl>=3.1.5; extra == 'dev'
 Requires-Dist: pandas>=2.2.3; extra == 'dev'
 Requires-Dist: plotly>=6.0.1; extra == 'dev'
 Requires-Dist: pydantic>=2.5.2; extra == 'dev'
-Requires-Dist: pytest>=9.0.2; extra == 'dev'
 Requires-Dist: pyyaml>=6.0.1; extra == 'dev'
 Requires-Dist: requests>=2.31.0; extra == 'dev'
 Requires-Dist: ruff>=0.1.7; extra == 'dev'
 Requires-Dist: twine>=4.0.2; extra == 'dev'
 Requires-Dist: urllib3>=2.1.0; extra == 'dev'
 Provides-Extra: notebook
-Requires-Dist: mlflow>=3.9.0; extra == 'notebook'
+Requires-Dist: mlflow>=2.19.0; extra == 'notebook'
 Description-Content-Type: text/markdown
 
 # Nextmv Python SDK

nextmv-1.0.0.dev1/nextmv/__about__.py

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

{nextmv-1.0.0 → nextmv-1.0.0.dev1}/nextmv/__entrypoint__.py

@@ -10,12 +10,13 @@ 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 = nextmv.Manifest.from_yaml(".")
+    manifest = cloud.Manifest.from_yaml(".")
 
     # Load the options from the manifest.
     options = manifest.extract_options()

{nextmv-1.0.0 → nextmv-1.0.0.dev1}/nextmv/__init__.py

@@ -11,6 +11,7 @@ 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
@@ -30,6 +31,7 @@ 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
@@ -48,6 +50,7 @@ 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
@@ -76,6 +79,7 @@ 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 → nextmv-1.0.0.dev1}/nextmv/cli/CONTRIBUTING.md

@@ -152,16 +152,14 @@ guidelines:
 - We embrace the use of emojis. They make the CLI friendlier and more
   approachable.
 - The `message.py` file contains helper functions for printing messages, like:
-  - `message`: prints a message. You can give it an emoji for the message. The
-    other commands have fixed emojis.
-  - `info`: prints an informational message. Use for neutral messages.
-  - `in_progress`: prints an in-progress message. Use before executing an action.
-  - `success`: prints a success message. Use after successfully completing an action.
-  - `warning`: prints a warning message. Use for non-critical issues.
-  - `error`: prints an error and raises an exception. Use for critical issues
-    and to return early from commands.
+  - `error`: prints an error and raises an exception.
+  - `success`: prints a success message.
+  - `warning`: prints a warning message.
+  - `in_progress`: prints an in-progress message.
+  - `info`: prints an informational message. You can give it an emoji for the
+    message. The other commands have fixed emojis.
 - For printing `JSON` information, use the `print_json` function in the
-  `message.py` file to print JSON output. This ensures consistent formatting
+  `messages.py` file to print JSON output. This ensures consistent formatting
   across the CLI.
 - Emojis should be formatted according to [Rich's emoji guide][rich-emoji].
   They are strings enclosed in colons, e.g. `:rocket:`, `:boom:`,
@@ -173,110 +171,40 @@ guidelines:
   success(f"Application [magenta]{app_id}[/magenta] deleted successfully.")
   ```
 
-- When showing the values of an `Enum`, use the `enum_values` function in the
-  `message.py` file which will give a nicely colored, comma-separated list of
-  the enum values. Consider the following example, where we get the allowed
-  values for the `InputFormat` class.
-
-  ```python
-      content_format: Annotated[
-        InputFormat | None,
-        typer.Option(
-            "--content-format",
-            "-c",
-            help=f"The content format for the instance. Allowed values are: {enum_values(InputFormat)}.",
-            metavar="CONTENT_FORMAT",
-            rich_help_panel="Instance configuration",
-        ),
-    ] = None,
-  ```
-
 ## Confirmation prompts
 
-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.
+For destructive actions (like deletions), use `rich.prompt.Confirm.ask()` to
+ask for user confirmation before proceeding. Follow these guidelines:
 
-When using confirmation prompts, follow these guidelines:
-
-- The confirmation message should use `[magenta]` for the variable/s being
+- The confirmation message should use `[magenta]` for the variable being
   affected.
-- Provide a `--yes` / `-y` flag to skip the confirmation prompt where possible,
-  useful for non-interactive sessions.
-- If the user declines, call `info()` and return early.
+- 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.
+- 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 = get_confirmation(
-        f"Are you sure you want to delete application [magenta]{app_id}[/magenta]? This action cannot be undone.",
+    confirm = Confirm.ask(
+        f"Are you sure you want to delete application [magenta]{app_id}[/magenta]? This action cannot be undone",
+        default=False,
     )
 
     if not confirm:
-        info(f"Application [magenta]{app_id}[/magenta] will not be deleted.")
+        info(msg=f"Application [magenta]{app_id}[/magenta] will not be deleted.", emoji=":bulb:")
         return
 ```
 
-## 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.
+## Formatting
 
-In any case, the best advice is to follow existing examples in the codebase to
-maintain consistency.
+Use these Rich markup guidelines when formatting help text and messages.
 
-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:
+- 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.
 
   ```python
   @app.command()
@@ -295,16 +223,16 @@ Here are some guidelines for when to use each formatting style.
       """
       Deletes a Nextmv Cloud application.
 
-      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 application with the ID [magenta]hare-app[/magenta].
-          $ [dim]nextmv cloud app delete --app-id hare-app[/dim]
+          $ [green]nextmv cloud app delete --app-id hare-app[/green]
 
       - Delete the application with the ID [magenta]hare-app[/magenta] without confirmation prompt.
-          $ [dim]nextmv cloud app delete --app-id hare-app --yes[/dim]
+          $ [green]nextmv cloud app delete --app-id hare-app --yes[/green]
       """
   ```
 
@@ -318,12 +246,6 @@ Here are some guidelines for when to use each formatting style.
   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:
@@ -343,6 +265,11 @@ Here are some guidelines for when to use each formatting style.
   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
@@ -389,15 +316,15 @@ to use it.
       [bold][underline]Examples[/underline][/bold]
 
       - Get the application with the ID [magenta]hare-app[/magenta].
-          $ [dim]nextmv cloud app get --app-id hare-app[/dim]
+          $ [green]nextmv cloud app get --app-id hare-app[/green]
 
       - Get the application with the ID [magenta]hare-app[/magenta] and save the information to an
         [magenta]app.json[/magenta] file.
-          $ [dim]nextmv cloud app get --app-id hare-app --output app.json[/dim]
+          $ [green]nextmv cloud app get --app-id hare-app --output app.json[/green]
       """
 
       client = build_client(profile)
-      in_progress("Getting application...")
+      info(msg="Getting application...", emoji=":hourglass_flowing_sand:")
 
       cloud_app = Application.get(
           client=client,
@@ -409,7 +336,7 @@ to use it.
           with open(output, "w") as f:
               json.dump(cloud_app_dict, f, indent=2)
 
-          success(f"Application information saved to [magenta]{output}[/magenta].")
+          success(msg=f"Application information saved to [magenta]{output}[/magenta].")
 
           return
 
@@ -426,10 +353,11 @@ 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 `[dim]` `[/dim]` tags.
+  - The command itself should be formatted using the `[green]` `[/green]` 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
@@ -438,8 +366,8 @@ to use it.
 
     ```text
     - Create an application with an ID and description.
-        $ [dim]nextmv cloud app create --name "Hare App" --app-id hare-app \\
-            --description "An application for routing hares"[/dim]
+        $ [green]nextmv cloud app create --name "Hare App" --app-id hare-app \\
+            --description "An application for routing hares"[/green]
     ```
 
 ## Command options

{nextmv-1.0.0 → nextmv-1.0.0.dev1}/nextmv/cli/cloud/__init__.py

@@ -16,8 +16,6 @@ from nextmv.cli.cloud.managed_input import app as managed_input_app
 from nextmv.cli.cloud.run import app as run_app
 from nextmv.cli.cloud.scenario import app as scenario_app
 from nextmv.cli.cloud.secrets import app as secrets_app
-from nextmv.cli.cloud.shadow import app as shadow_app
-from nextmv.cli.cloud.switchback import app as switchback_app
 from nextmv.cli.cloud.upload import app as upload_app
 from nextmv.cli.cloud.version import app as version_app
 
@@ -35,8 +33,6 @@ app.add_typer(managed_input_app, name="managed-input")
 app.add_typer(run_app, name="run")
 app.add_typer(scenario_app, name="scenario")
 app.add_typer(secrets_app, name="secrets")
-app.add_typer(shadow_app, name="shadow")
-app.add_typer(switchback_app, name="switchback")
 app.add_typer(upload_app, name="upload")
 app.add_typer(version_app, name="version")
 

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

@@ -27,22 +27,24 @@ 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 --input-set-id option to create a new batch experiment.
+    provide the [code]--input-set-id[/code] option to create a new batch
+    experiment.
 
-    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.
+    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.
 
     [bold][underline]Metrics[/underline][/bold]
 
     Metrics are provided as [magenta]json[/magenta] objects using the
-    --metrics flag. Each metric defines how to compare the
+    [code]--metrics[/code] 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 --metrics flag.
-    - Multiple metrics as a [magenta]json[/magenta] array in a single --metrics flag.
+    - Multiple metrics by repeating the [code]--metrics[/code] flag.
+    - Multiple metrics as a [magenta]json[/magenta] array in a single [code]--metrics[/code] flag.
 
     Each metric must have the following fields:
     - [magenta]field[/magenta]: Field of the metric to measure (e.g., "solution.objective").
@@ -55,7 +57,7 @@ app = typer.Typer()
     - [magenta]statistic[/magenta]: Statistical method. Allowed values: {enum_values(StatisticType)}.
 
     Object format:
-    [dim]{{
+    [green]{{
         "field": "field",
         "metric_type": "type",
         "params": {{
@@ -66,12 +68,12 @@ app = typer.Typer()
             }}
         }},
         "statistic": "statistic"
-    }}[/dim]
+    }}[/green]
 
     [bold][underline]Examples[/underline][/bold]
 
     - Create an acceptance test with a single metric.
-        $ [dim]METRIC='{{
+        $ [green]METRIC='{{
             "field": "solution.objective",
             "metric_type": "direct-comparison",
             "params": {{
@@ -82,10 +84,10 @@ 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[/dim]
+            --metrics "$METRIC" --input-set-id input-set-123[/green]
 
     - Create with multiple metrics by repeating the flag.
-        $ [dim]METRIC1='{{
+        $ [green]METRIC1='{{
             "field": "solution.objective",
             "metric_type": "direct-comparison",
             "params": {{
@@ -105,10 +107,10 @@ 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[/dim]
+            --metrics "$METRIC1" --metrics "$METRIC2" --input-set-id input-set-123[/green]
 
     - Create with multiple metrics in a single [magenta]json[/magenta] array.
-        $ [dim]METRICS='[
+        $ [green]METRICS='[
             {{
                 "field": "solution.objective",
                 "metric_type": "direct-comparison",
@@ -130,10 +132,10 @@ 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[/dim]
+            --metrics "$METRICS" --input-set-id input-set-123[/green]
 
     - Create an acceptance test and wait for it to complete.
-        $ [dim]METRIC='{{
+        $ [green]METRIC='{{
             "field": "solution.objective",
             "metric_type": "direct-comparison",
             "params": {{
@@ -144,10 +146,10 @@ 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[/dim]
+            --metrics "$METRIC" --input-set-id input-set-123 --wait[/green]
 
     - Create an acceptance test and save the results to a file, waiting for completion.
-        $ [dim]METRIC='{{
+        $ [green]METRIC='{{
             "field": "solution.objective",
             "metric_type": "direct-comparison",
             "params": {{
@@ -158,7 +160,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[/dim]
+            --metrics "$METRIC" --input-set-id input-set-123 --output results.json[/green]
     """
 )
 def create(
@@ -263,7 +265,7 @@ def create(
             "--wait",
             "-w",
             help="Wait for the acceptance test to complete. Results are printed to [magenta]stdout[/magenta]. "
-            "Specify output location with --output.",
+            "Specify output location with [code]--output[/code].",
             rich_help_panel="Output control",
         ),
     ] = False,

{nextmv-1.0.0 → nextmv-1.0.0.dev1}/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,28 +32,32 @@ 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 --yes 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 [code]--yes[/code] 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].
-        $ [dim]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail[/dim]
+        $ [green]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail[/green]
 
     - Delete the acceptance test without confirmation prompt.
-        $ [dim]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail --yes[/dim]
+        $ [green]nextmv cloud acceptance delete --app-id hare-app --acceptance-test-id test-cotton-tail --yes[/green]
     """
 
     if not yes:
-        confirm = get_confirmation(
+        confirm = Confirm.ask(
             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:
-            info(f"Acceptance test [magenta]{acceptance_test_id}[/magenta] will not be deleted.")
+            info(
+                msg=f"Acceptance test [magenta]{acceptance_test_id}[/magenta] will not be deleted.",
+                emoji=":bulb:",
+            )
             return
 
     cloud_app = build_app(app_id=app_id, profile=profile)

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

{nextmv-1.0.0 → nextmv-1.0.0.dev1}/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].
-        $ [dim]nextmv cloud acceptance list --app-id hare-app[/dim]
+        $ [green]nextmv cloud acceptance list --app-id hare-app[/green]
 
     - List all acceptance tests and save to a file.
-        $ [dim]nextmv cloud acceptance list --app-id hare-app --output tests.json[/dim]
+        $ [green]nextmv cloud acceptance list --app-id hare-app --output tests.json[/green]
 
     - List all acceptance tests using a specific profile.
-        $ [dim]nextmv cloud acceptance list --app-id hare-app --profile prod[/dim]
+        $ [green]nextmv cloud acceptance list --app-id hare-app --profile prod[/green]
     """
 
     cloud_app = build_app(app_id=app_id, profile=profile)

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

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

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

@@ -20,9 +20,9 @@ app.add_typer(update_app)
 @app.callback()
 def callback() -> None:
     """
-    Manage SSO for your Nextmv Cloud account (organization).
+    Manage 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