yellowdog-python-examples 7.8.8__tar.gz → 7.9.0__tar.gz

{yellowdog_python_examples-7.8.8/yellowdog_python_examples.egg-info → yellowdog_python_examples-7.9.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: yellowdog-python-examples
-Version: 7.8.8
+Version: 7.9.0
 Summary: Example Python commands using the YellowDog Python SDK
 Home-page: https://github.com/yellowdog/python-examples
 Author: YellowDog Limited
@@ -43,6 +43,7 @@ The command scripts support:
 
 - **Provisioning** Worker Pools with the **`yd-provision`** command
 - **Submitting** Work Requirements with the **`yd-submit`** command
+- **Starting** HELD Work Requirements and **Holding** (or pausing) RUNNING Work Requirements with the **`yd-start`** and **`yd-hold`** commands
 - **Uploading** files to the YellowDog Object Store with the **`yd-upload`** command
 - **Instantiating** Compute Requirements with the **`yd-instantiate`** command
 - **Downloading** Results from the YellowDog Object Store with the **`yd-download`** command
@@ -52,7 +53,9 @@ The command scripts support:
 - **Terminating** Compute Requirements with the **`yd-terminate`** command
 - **Deleting** objects in the YellowDog Object Store with the **`yd-delete`** command
 - **Listing** YellowDog items using the **`yd-list`** command
-- **Resizing** Worker Pools and Compute Requirements
-- **Creating, Updating and Removing** Source Templates, Compute Templates, Keyrings, Credentials, Namespace Storage Configurations, Image Families, and Configured Worker Pools
+- **Resizing** Worker Pools and Compute Requirements with the **`yd-resize`** command
+- **Boosting** Allowances with the **`yd-boost`** command
+- **Creating, Updating and Removing** Source Templates, Compute Templates, Keyrings, Credentials, Namespace Storage Configurations, Image Families, Allowances, and Configured Worker Pools with the **`yd-create`** and **`yd-remove`** commands
+- **Following Event Streams** for Work Requirements, Worker Pools and Compute Requirements with the **`yd-follow`** command
 
-Please see the [GitHub repository](https://github.com/yellowdog/python-examples) for more details.
+Please see the documenation in the [GitHub repository](https://github.com/yellowdog/python-examples) for more details.

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/PYPI_README.md

@@ -8,6 +8,7 @@ The command scripts support:
 
 - **Provisioning** Worker Pools with the **`yd-provision`** command
 - **Submitting** Work Requirements with the **`yd-submit`** command
+- **Starting** HELD Work Requirements and **Holding** (or pausing) RUNNING Work Requirements with the **`yd-start`** and **`yd-hold`** commands
 - **Uploading** files to the YellowDog Object Store with the **`yd-upload`** command
 - **Instantiating** Compute Requirements with the **`yd-instantiate`** command
 - **Downloading** Results from the YellowDog Object Store with the **`yd-download`** command
@@ -17,7 +18,9 @@ The command scripts support:
 - **Terminating** Compute Requirements with the **`yd-terminate`** command
 - **Deleting** objects in the YellowDog Object Store with the **`yd-delete`** command
 - **Listing** YellowDog items using the **`yd-list`** command
-- **Resizing** Worker Pools and Compute Requirements
-- **Creating, Updating and Removing** Source Templates, Compute Templates, Keyrings, Credentials, Namespace Storage Configurations, Image Families, and Configured Worker Pools
+- **Resizing** Worker Pools and Compute Requirements with the **`yd-resize`** command
+- **Boosting** Allowances with the **`yd-boost`** command
+- **Creating, Updating and Removing** Source Templates, Compute Templates, Keyrings, Credentials, Namespace Storage Configurations, Image Families, Allowances, and Configured Worker Pools with the **`yd-create`** and **`yd-remove`** commands
+- **Following Event Streams** for Work Requirements, Worker Pools and Compute Requirements with the **`yd-follow`** command
 
-Please see the [GitHub repository](https://github.com/yellowdog/python-examples) for more details.
+Please see the documenation in the [GitHub repository](https://github.com/yellowdog/python-examples) for more details.

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/README.md

@@ -87,6 +87,7 @@
    * [Namespace Storage Configurations](#namespace-storage-configurations)
    * [Configured Worker Pools](#configured-worker-pools)
    * [Allowances](#allowances)
+   * [String Attribute Definitions](#string-attribute-definitions)
 * [Jsonnet Support](#jsonnet-support)
    * [Jsonnet Installation](#jsonnet-installation)
    * [Variable Substitutions in Jsonnet Files](#variable-substitutions-in-jsonnet-files)
@@ -114,7 +115,7 @@
    * [yd-boost](#yd-boost)
 
 <!-- Created by https://github.com/ekalinin/github-markdown-toc -->
-<!-- Added by: pwt, at: Fri Apr 19 11:43:37 BST 2024 -->
+<!-- Added by: pwt, at: Wed May  8 16:37:54 BST 2024 -->
 
 <!--te-->
 
@@ -156,6 +157,8 @@ Run any command with the `--help`/`-h` option to discover the command's options.
 
 # YellowDog Prerequisites
 
+(See also the quick start guides for [Provisioned](https://github.com/yellowdog/python-examples-templates/blob/main/quickstart.md) and [Configured](https://github.com/yellowdog/python-examples-templates/blob/main/quickstart-configured.md) Worker Pools.)
+
 To submit **Work Requirements** to YellowDog for processing by Configured Worker Pools (on-premise) and/or Provisioned Worker Pools (cloud-provisioned resources), you'll need:
 
 1. A YellowDog Platform Account.
@@ -176,7 +179,7 @@ To set up **Configured Worker Pools**, you'll need:
 5. A Configured Worker Pool Token: from the **Workers** tab in the [YellowDog Portal](https://portal.yellowdog.co/#/workers), use the **+Add Configured Worker Pool** button to create a new Worker Pool and generate a token.
 
 
-6. Obtain the YellowDog Agent and install/configure it on your on-premise systems using the Token above.
+6. Obtain the YellowDog Agent and install/configure it on your on-premise systems using the Token obtained above. See guidance for [Linux](https://github.com/yellowdog/resources/blob/main/agent-install/linux/README.md) and [Windows](https://github.com/yellowdog/resources/blob/main/agent-install/windows/README-CONFIGURED.md).
 
 # Script Installation with Pip
 
@@ -391,21 +394,25 @@ Substitutions can also be performed for non-string (number, boolean, array, and
 
 The following substitutions are automatically created and can be used in any section of the configuration file, or in any JSON specification:
 
-| Directive       | Description                                                              | Example of Substitution |
-|:----------------|:-------------------------------------------------------------------------|:------------------------|
-| `{{username}}`  | The current user's login username, lower case, spaces replaced           | jane_smith              |
-| `{{date}}`      | The current date (UTC): YYYYMMDD                                         | 20221027                |
-| `{{time}}`      | The current time (UTC): HHMMSSss                                         | 16302699                |
-| `{{datetime}}`  | Concatenation of the date and time, with a '-' separator                 | 20221027-163026         |
-| `{{random}}`    | A random, three digit hexadecimal number (lower case)                    | a1c                     |
-| `{{namespace}}` | The `namespace` property.                                                | my_namespace            |
-| `{{tag}}`       | The `tag` property.                                                      | my_tag                  |
-| `{{key}}`       | The application `key` property.                                          |                         |
-| `{{secret}}`    | The application `secret` property.                                       |                         |
-| `{{url}}`       | The Platform `url` property.                                             |                         |
+| Directive             | Description                                                    | Example of Substitution |
+|:----------------------|:---------------------------------------------------------------|:------------------------|
+| `{{username}}`        | The current user's login username, lower case, spaces replaced | jane_smith              |
+| `{{date}}`            | The current date (UTC): YYYYMMDD                               | 20221027                |
+| `{{time}}`            | The current time (UTC): HHMMSSss                               | 16302699                |
+| `{{datetime}}`        | Concatenation of the date and time, with a '-' separator       | 20221027-163026         |
+| `{{random}}`          | A random, three digit hexadecimal number (lower case)          | a1c                     |
+| `{{namespace}}`       | The `namespace` property.                                      | my_namespace            |
+| `{{tag}}`             | The `tag` property.                                            | my_tag                  |
+| `{{key}}`             | The application `key` property.                                |                         |
+| `{{secret}}`          | The application `secret` property.                             |                         |
+| `{{url}}`             | The Platform `url` property.                                   |                         |
+| `{{config_dir_abs}}`  | The absolute directory path of the configuration file          | /yellowdog/workloads    |
+| `{{config_dir_name}}` | The immediate containing directory of the configuration file   | workloads               |
 
 For the `date`, `time`, `datetime` and `random` directives, the same values will be used for the duration of a command -- i.e., if `{{time}}` is used within multiple properties, the identical value will be used for each substitution.
 
+The `config_dir_` substitutions use the name of the directory containing the nominated TOML configuration file, or the invocation directory if no configuration file is supplied.
+
 ## User-Defined Variables
 
 User-defined variables can be supplied using an option on the command line, or by setting environment variables prefixed with `YD_VAR_`, or by including the directives in the `[common]` section of the TOML configuration file.
@@ -413,7 +420,7 @@ User-defined variables can be supplied using an option on the command line, or b
 1. The **command line** option is `--variable` (or `-v`). For example, `yd-submit -v project_code=pr-213-a -v run_id=1234` will establish two new variables that can be used as `{{project_code}}` and `{{run_id}}`, which will be substituted by `pr-213-a` and `1234` respectively.
 
 
-2. For **environment variables**, setting the variable `YD_VAR_project_code="pr-213-a"` will create a new variable that can be used as `{{project_code}}`, which will be substituted by `pr-213-a`.
+2. For **environment variables**, setting the variable `YD_VAR_project_code="pr-213-a"` will create a new variable that can be used as `{{project_code}}`, which will be substituted by `pr-213-a`. Note that if running on Windows, all environment variable names are case-insensitive and converted to upper case, so choose upper case variable names only.
 
 
 3. For **setting within the TOML file**, include a **`variables`** table in the `[common]` section of the file. E.g., `variables = {project_code = "pr-213a", run_id = "1234"}`. Note that this can also use the form:
@@ -662,7 +669,7 @@ inputs = ["my_bash_script.sh"]
 arguments = ["{{wr_name}}/my_bash_script.sh", "1", "2", "3"]
 ```
 
-In the case of Windows batch (`.bat`) files, a `/c` flag is prepended to the `cmd.exe` argument list to ensure correct execution bahaviour. For example:
+In the case of Windows batch (`.bat`) files, a `/c` flag is prepended to the `cmd.exe` argument list to ensure correct execution behaviour. For example:
 
 ```toml
 taskType = "cmd"  # or "bat"
@@ -1023,11 +1030,10 @@ A simple example of the JSON output is shown below, showing a Work Requirement w
 `% yd-submit --dry-run --quiet`
 ```json
 {
-  "fulfilOnSubmit": false,
-  "name": "pyex-bash_230114-095504-53a",
-  "namespace": "pyexamples",
+  "name": "pyex-bash-pwt2_240424-12051160",
+  "namespace": "pyexamples-pwt2",
   "priority": 0,
-  "tag": "pyex-bash",
+  "tag": "pyex-bash-pwt2",
   "taskGroups": [
     {
       "finishIfAllTasksFinished": true,
@@ -1035,22 +1041,33 @@ A simple example of the JSON output is shown below, showing a Work Requirement w
       "name": "task_group_1",
       "priority": 0,
       "runSpecification": {
-        "maximumTaskRetries": 0,
+        "maximumTaskRetries": 5,
         "taskTypes": ["bash"],
-        "workerTags": ["pyex-bash"]
+        "workerTags": ["pyex-bash-pwt2-worker", "onpremise-pwt2"]
       },
+      "starved": false,
+      "waitingOnDependency": false,
       "tasks": [
         {
-          "arguments": ["pyex-bash_230114-095504-53a/sleep_script.sh"],
-          "environment": {},
+          "arguments": ["pyex-bash-pwt2_240424-12051160/sleep_script.sh", 1, 2, 3],
+          "environment": {
+            "TEST_ENV_1": "100",
+            "TEST_ENV_2": "200",
+            "YD_TASK_NAME": "task_1",
+            "YD_TASK_NUMBER": "1",
+            "YD_TASK_GROUP_NAME": "task_group_1",
+            "YD_TASK_GROUP_NUMBER": "1",
+            "YD_WORK_REQUIREMENT_NAME": "pyex-bash-pwt2_240424-12051160",
+            "YD_NAMESPACE": "pyexamples-pwt2"
+          },
           "inputs": [
             {
-              "objectNamePattern": "pyex-bash_230114-095504-53a/sleep_script.sh",
+              "objectNamePattern": "pyex-bash-pwt2_240424-12051160/sleep_script.sh",
               "source": "TASK_NAMESPACE",
-              "verification": "VERIFY_WAIT"
+              "verification": "VERIFY_AT_START"
             }
           ],
-          "name": "task_01",
+          "name": "task_1",
           "outputs": [
             {"alwaysUpload": true, "required": false, "source": "PROCESS_OUTPUT"}
           ],
@@ -1587,13 +1604,13 @@ Here's an example of the `workerPool` section of a TOML configuration file, show
     templateId = "ydid:crt:D9C548:465a107c-7cea-46e3-9fdd-15116cb92c40"
     # Note: only one of 'userData'/'userDataFile'/'userDataFiles' should be set
     userData = ""
-    userDataFile = "myuserdata.txt"
-    userDataFiles = ["myuserdata1.txt", "myuserdata2.txt"]
+    # userDataFile = "myuserdata.txt"
+    # userDataFiles = ["myuserdata1.txt", "myuserdata2.txt"]
     workerTag = "tag-{{username}}"
     # Specify either workersPerNode or workersPerVCPU
     workersPerNode = 1
-    workersPerVCPU = 1
-#   workerPoolData = "worker_pool.json"
+    # workersPerVCPU = 1
+    # workerPoolData = "worker_pool.json"  # Optionally specify worker pool JSON specification
 ```
 
 ## Worker Pool Specification Using JSON Documents
@@ -1782,6 +1799,7 @@ The commands **yd-create** and **yd-remove** allow the creation, update and remo
 - Namespace Storage Configurations
 - Configured Worker Pools
 - Allowances
+- String Attribute Definitions
 
 ## Overview of Operation
 
@@ -2145,6 +2163,24 @@ When using `yd-remove`, Allowances are again matched using their `description` p
 
 Allowances can be **boosted** (have extra hours added to the Allowance) using the `yd-boost` command.
 
+## String Attribute Definitions
+
+The Attribute Definition example and schema can be found at: https://docs.yellowdog.co/api/?spec=Compute%20API#tag/compute/post/compute/attributes/user. Currently, only **String Attribute Definitions** are supported.
+
+Example:
+
+```json
+{
+  "resource": "StringAttributeDefinition",
+  "name": "user.my-attribute",
+  "title": "My attribute title",
+  "description": "This is a description of my attribute",
+  "options": ["yes", "no", "maybe"]
+}
+```
+
+The `name` and `title` properties are required, while the rest are optional. The `user.` prefix is required when specifying the `name` property.
+
 # Jsonnet Support
 
 In all circumstances where JSON files are used by the Python Examples commands,  **[Jsonnet](https://jsonnet.org)** files can be used instead. This allows the use of Jsonnet's powerful JSON extensions, including comments, variables, functions, etc.

yellowdog_python_examples-7.9.0/yd_commands/__init__.py

@@ -0,0 +1 @@
+__version__ = "7.9.0"

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/yd_commands/create.py

@@ -10,7 +10,7 @@ from typing import Dict, List, Optional
 
 import yellowdog_client.model as model
 from dateparser import parse as date_parse
-from requests import post
+from requests import post, put
 from requests.exceptions import HTTPError
 from yellowdog_client.model import (
     AccountAllowance,
@@ -54,6 +54,7 @@ from yd_commands.settings import (
     RN_REQUIREMENT_TEMPLATE,
     RN_SOURCE_TEMPLATE,
     RN_STORAGE_CONFIGURATION,
+    RN_STRING_ATTRIBUTE_DEFINITION,
 )
 from yd_commands.wrapper import ARGS_PARSER, CLIENT, CONFIG_COMMON, main_wrapper
 
@@ -118,6 +119,8 @@ def create_resources(
                 create_configured_worker_pool(resource)
             elif resource_type == RN_ALLOWANCE:
                 create_allowance(resource)
+            elif resource_type == RN_STRING_ATTRIBUTE_DEFINITION:
+                create_string_attribute_definition_via_api(resource)
             else:
                 print_error(f"Unknown resource type '{resource_type}'")
         except Exception as e:
@@ -789,6 +792,45 @@ def _get_model_class(class_name: str):
     return getattr(model, class_name)
 
 
+def create_string_attribute_definition_via_api(resource: Dict):
+    """
+    Use the API to create/update user string attribute definitions.
+    """
+    try:
+        name = resource["name"]
+        title = resource["title"]
+    except KeyError as e:
+        raise Exception(f"Expected property to be defined ({e})")
+
+    url = f"{CONFIG_COMMON.url}/compute/attributes/user"
+    headers = {"Authorization": f"yd-key {CONFIG_COMMON.key}:{CONFIG_COMMON.secret}"}
+    payload = {
+        "name": name,
+        "title": title,
+        "type": "co.yellowdog.platform.model.StringAttributeDefinition",
+        "description": resource.get("description", ""),
+        "options": resource.get("options", []),
+    }
+
+    # Attempt attribute creation
+    response = post(url=url, headers=headers, json=payload)
+
+    if response.status_code == 200:
+        print_log(f"Created new String Attribute Definition '{name}'")
+        return
+
+    if "Attribute already exists" in response.text:
+        if not confirmed(f"Update existing String Attribute Definition '{name}'?"):
+            return
+
+        response = put(url=url, headers=headers, json=payload)
+        if response.status_code == 200:
+            print_log(f"Updated existing String Attribute Definition '{name}'")
+            return
+
+    raise Exception(f"HTTP {response.status_code} ({response.text})")
+
+
 # Entry point
 if __name__ == "__main__":
     main()

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/yd_commands/load_config.py

@@ -4,7 +4,8 @@ Common utility functions, mostly related to loading configuration data.
 
 import os
 from os import getenv
-from os.path import dirname, join, relpath
+from os.path import abspath, dirname, join, relpath
+from pathlib import Path
 from sys import exit
 from typing import Dict, Optional
 
@@ -49,6 +50,11 @@ CONFIG_FILE = relpath(
 
 try:
     CONFIG_FILE_DIR = dirname(CONFIG_FILE)
+    config_dir_abs = abspath(CONFIG_FILE_DIR)
+    config_dir_short = Path(config_dir_abs).parts[-1]
+    VARIABLE_SUBSTITUTIONS.update(
+        {"config_dir_abs": config_dir_abs, "config_dir_name": config_dir_short}
+    )
     print_log(f"Loading configuration data from: '{CONFIG_FILE}'")
     CONFIG_TOML: Dict = load_toml_file_with_variable_substitutions(CONFIG_FILE)
     try:

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/yd_commands/load_resources.py

@@ -16,6 +16,7 @@ from yd_commands.settings import (
     RN_REQUIREMENT_TEMPLATE,
     RN_SOURCE_TEMPLATE,
     RN_STORAGE_CONFIGURATION,
+    RN_STRING_ATTRIBUTE_DEFINITION,
 )
 from yd_commands.variables import (
     load_json_file_with_variable_substitutions,
@@ -94,6 +95,7 @@ def _resequence_resources(
         RN_KEYRING,
         RN_CREDENTIAL,
         RN_IMAGE_FAMILY,
+        RN_STRING_ATTRIBUTE_DEFINITION,
         RN_SOURCE_TEMPLATE,
         RN_REQUIREMENT_TEMPLATE,
         RN_ALLOWANCE,

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/yd_commands/remove.py

@@ -7,6 +7,7 @@ A script to remove YellowDog resources.
 from copy import deepcopy
 from typing import Dict, List, Optional
 
+from requests import delete
 from requests.exceptions import HTTPError
 from yellowdog_client.model import (
     MachineImage,
@@ -34,8 +35,9 @@ from yd_commands.settings import (
     RN_REQUIREMENT_TEMPLATE,
     RN_SOURCE_TEMPLATE,
     RN_STORAGE_CONFIGURATION,
+    RN_STRING_ATTRIBUTE_DEFINITION,
 )
-from yd_commands.wrapper import ARGS_PARSER, CLIENT, main_wrapper
+from yd_commands.wrapper import ARGS_PARSER, CLIENT, CONFIG_COMMON, main_wrapper
 
 
 @main_wrapper
@@ -92,6 +94,8 @@ def remove_resources(resources: Optional[List[Dict]] = None):
                         "alternatively, Allowances can be removed by their "
                         "YellowDog IDs (yd-remove --ids)"
                     )
+            elif resource_type == RN_STRING_ATTRIBUTE_DEFINITION:
+                remove_string_attribute_definition_via_api(resource)
             else:
                 print_error(f"Unknown resource type '{resource_type}'")
         except Exception as e:
@@ -407,6 +411,29 @@ def remove_resource_by_id(resource_id: str):
         print_error(f"Unable to remove resource with ID {resource_id}: {e}")
 
 
+def remove_string_attribute_definition_via_api(resource: Dict):
+    """
+    Use the API to remove user string attribute definitions.
+    """
+    try:
+        name = resource["name"]
+    except KeyError as e:
+        raise Exception(f"Expected property to be defined ({e})")
+
+    if not confirmed(f"Remove String Attribute Definition '{name}'?"):
+        return
+
+    url = f"{CONFIG_COMMON.url}/compute/attributes/user/{name}"
+    headers = {"Authorization": f"yd-key {CONFIG_COMMON.key}:{CONFIG_COMMON.secret}"}
+    response = delete(url=url, headers=headers)
+
+    if response.status_code == 200:
+        print_log(f"Removed String Attribute Definition '{name}' (if present)")
+        return
+
+    raise Exception(f"HTTP {response.status_code} ({response.text})")
+
+
 # Entry point
 if __name__ == "__main__":
     main()

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/yd_commands/settings.py

@@ -105,3 +105,4 @@ RN_KEYRING = "Keyring"
 RN_REQUIREMENT_TEMPLATE = "ComputeRequirementTemplate"
 RN_SOURCE_TEMPLATE = "ComputeSourceTemplate"
 RN_STORAGE_CONFIGURATION = "NamespaceStorageConfiguration"
+RN_STRING_ATTRIBUTE_DEFINITION = "StringAttributeDefinition"

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0}/yd_commands/shutdown.py

@@ -32,9 +32,11 @@ def main():
         return
 
     print_log(
-        "Shutting down Worker Pools with Compute Requirements in "
+        "Shutting down Provisioned Worker Pools with Compute Requirements in "
         f"namespace '{CONFIG_COMMON.namespace}' and "
-        f"tag starting with '{CONFIG_COMMON.name_tag}'"
+        f"tag starting with '{CONFIG_COMMON.name_tag}' "
+        "(or Configured Worker Pools with names starting with "
+        f"'{CONFIG_COMMON.name_tag}')"
     )
     worker_pool_summaries: List[WorkerPoolSummary] = (
         CLIENT.worker_pool_client.find_all_worker_pools()
@@ -43,11 +45,19 @@ def main():
 
     selected_worker_pool_summaries: List[WorkerPoolSummary] = []
     for worker_pool_summary in worker_pool_summaries:
-        if not (
-            "ProvisionedWorkerPool" not in worker_pool_summary.type
-            or worker_pool_summary.status
-            in [WorkerPoolStatus.TERMINATED, WorkerPoolStatus.SHUTDOWN]
-        ):
+        if worker_pool_summary.status not in [
+            WorkerPoolStatus.TERMINATED,
+            WorkerPoolStatus.SHUTDOWN,
+        ]:
+            if "ProvisionedWorkerPool" not in worker_pool_summary.type:
+                # Configured Worker Pool: check worker pool name only
+                if (
+                    worker_pool_summary.name is not None
+                    and worker_pool_summary.name.startswith(CONFIG_COMMON.name_tag)
+                ):
+                    selected_worker_pool_summaries.append(worker_pool_summary)
+                continue
+
             worker_pool: WorkerPool = get_worker_pool_by_id(
                 CLIENT, worker_pool_summary.id
             )

{yellowdog_python_examples-7.8.8 → yellowdog_python_examples-7.9.0/yellowdog_python_examples.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: yellowdog-python-examples
-Version: 7.8.8
+Version: 7.9.0
 Summary: Example Python commands using the YellowDog Python SDK
 Home-page: https://github.com/yellowdog/python-examples
 Author: YellowDog Limited
@@ -43,6 +43,7 @@ The command scripts support:
 
 - **Provisioning** Worker Pools with the **`yd-provision`** command
 - **Submitting** Work Requirements with the **`yd-submit`** command
+- **Starting** HELD Work Requirements and **Holding** (or pausing) RUNNING Work Requirements with the **`yd-start`** and **`yd-hold`** commands
 - **Uploading** files to the YellowDog Object Store with the **`yd-upload`** command
 - **Instantiating** Compute Requirements with the **`yd-instantiate`** command
 - **Downloading** Results from the YellowDog Object Store with the **`yd-download`** command
@@ -52,7 +53,9 @@ The command scripts support:
 - **Terminating** Compute Requirements with the **`yd-terminate`** command
 - **Deleting** objects in the YellowDog Object Store with the **`yd-delete`** command
 - **Listing** YellowDog items using the **`yd-list`** command
-- **Resizing** Worker Pools and Compute Requirements
-- **Creating, Updating and Removing** Source Templates, Compute Templates, Keyrings, Credentials, Namespace Storage Configurations, Image Families, and Configured Worker Pools
+- **Resizing** Worker Pools and Compute Requirements with the **`yd-resize`** command
+- **Boosting** Allowances with the **`yd-boost`** command
+- **Creating, Updating and Removing** Source Templates, Compute Templates, Keyrings, Credentials, Namespace Storage Configurations, Image Families, Allowances, and Configured Worker Pools with the **`yd-create`** and **`yd-remove`** commands
+- **Following Event Streams** for Work Requirements, Worker Pools and Compute Requirements with the **`yd-follow`** command
 
-Please see the [GitHub repository](https://github.com/yellowdog/python-examples) for more details.
+Please see the documenation in the [GitHub repository](https://github.com/yellowdog/python-examples) for more details.

yellowdog_python_examples-7.8.8/yd_commands/__init__.py

@@ -1 +0,0 @@
-__version__ = "7.8.8"