Merge pull request #145 from globus/release/0.14.0

Release/0.14.0

.pre-commit-config.yaml

@@ -2,21 +2,21 @@
 # See https://pre-commit.com/hooks.html for more hooks
 repos:
 - repo: https://github.com/pre-commit/pre-commit-hooks
-  rev: v4.0.1
+  rev: v4.1.0
   hooks:
   - id: trailing-whitespace
   - id: end-of-file-fixer
   - id: check-yaml
   - id: check-added-large-files
 
 - repo: https://github.com/psf/black
-  rev: 21.12b0
+  rev: 22.3.0
   hooks:
   - id: black-jupyter
     language_version: python3
 
 - repo: https://github.com/pycqa/isort
-  rev: 5.8.0
+  rev: 5.10.1
   hooks:
     - id: isort
       name: isort (python)

CHANGELOG.rst

@@ -10,6 +10,29 @@ Unreleased changes are documented in files in the `changelog.d`_ directory.
 
 ..  scriv-insert-here
 
+0.14.0 — 2022-03-25
+===================
+
+Features
+--------
+
+-   `[sc-13426] <https://app.shortcut.com/globus/story/13426>`_
+    Support setting tags when using the ``flow run`` subcommand.
+-   Support batch updates of one or more Runs.
+-   Support updating tags and labels using the ``flow run-update`` subcommand.
+-   Support erasing the list of Run managers and Run monitors using the ``flow run-update`` subcommand.
+    This can be done by specifying an empty string for the value of the ``--run-manager`` and ``--run-monitor`` options.
+
+Bugfixes
+--------
+
+-   `[sc-13664] <https://app.shortcut.com/globus/story/13664/>`_
+    Fix tabular ``run-list`` output.
+-   `[sc-14109] <https://app.shortcut.com/globus/story/14109>`_
+    Mark the ``run-status`` subcommand's ``--flow-id`` option as a mandatory UUID.
+-   `[sc-14127] <https://app.shortcut.com/globus/story/14127>`_
+    Prevent a validation error that occurs when an input schema is not provided to the ``flow deploy`` subcommand.
+
 0.13.1 — 2022-03-02
 ===================
 

docs/source/authoring_flows.rst

@@ -516,8 +516,8 @@ Example Flows
 
 .. _example-flow-move:
 
-"Move" Flow
-^^^^^^^^^^^
+"Move (Globus Example)"
+^^^^^^^^^^^^^^^^^^^^^^^
 
 Flow ID: ``9123c20b-61e0-46e8-9469-92c999b6b8f2``.
 
@@ -526,52 +526,67 @@ from a source to a destination and then deleting the directory from the source.
 The entire directory's contents, including files and subdirectories, will be
 moved to the destination and then removed from the source.
 
+Note that this flow requires at least one of the collections to be managed under a Globus subscription.
+
 View the `Move flow definition`_ in the Globus web app.
 (You may need to log in first.)
 
 .. code-block:: json
     :caption: Example Input
 
     {
-        "source_endpoint_id": "ddb59af0-6d04-11e5-ba46-22000b92c6ec",
-        "source_path": "/~/source-directory",
-        "destination_endpoint_id": "ddb59aef-6d04-11e5-ba46-22000b92c6ec",
-        "destination_path": "/~/destination-directory",
-        "transfer_label": "Transfer for Generic Move from Globus Tutorial Endpoint 2 to Globus Tutorial Endpoint 1",
-        "delete_label": "Delete after Transfer for Generic Move from Globus Tutorial Endpoint 2 to Globus Tutorial Endpoint 1"
+        "source": {
+          "id": "ddb59aef-6d04-11e5-ba46-22000b92c6ec",
+          "path": "/~/source-directory"
+        },
+        "destination": {
+          "id": "ddb59af0-6d04-11e5-ba46-22000b92c6ec",
+          "path": "/~/destination-directory"
+        }
+        "transfer_label": "Transfer for Generic Move from Globus Tutorial Endpoint 1 to Globus Tutorial Endpoint 2",
+        "delete_label": "Delete after Transfer for Generic Move from Globus Tutorial Endpoint 1 to Globus Tutorial Endpoint 2"
     }
 
-(Choose different ``source_path`` and ``destination_path`` as needed to run this
-example flow.)
+(Choose different ``source.path`` and ``destination.path`` as needed to run this example flow.)
 
 .. _example-flow-2-stage-transfer:
 
-"2 Stage Transfer" Flow
-^^^^^^^^^^^^^^^^^^^^^^^
+"2 Stage Transfer (Globus Example)"
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Flow ID: ``79a4653f-f8da-43b6-a581-5d3b345ad575``.
 
 Transfer from source to destination with an intermediate endpoint in-between.
 Remove from intermediate after completion.
 
+Note that this flow requires at least one of the collections to be managed under a Globus subscription.
+
 View the `2 Stage Transfer flow definition`_ in the Globus web app.
 
 .. code-block:: json
     :caption: Example Input
 
     {
-        "source_endpoint_id": "ddb59af0-6d04-11e5-ba46-22000b92c6ec",
-        "source_path": "/~/source-directory",
-        "intermediate_endpoint_id": "ddb59af0-6d04-11e5-ba46-22000b92c6ec",
-        "intermediate_path": "/~/intermediate-directory-which-will-be-removed",
-        "destination_endpoint_id": "ddb59aef-6d04-11e5-ba46-22000b92c6ec",
-        "destination_path": "/~/destination-directory",
+        "source": {
+          "id": "ddb59aef-6d04-11e5-ba46-22000b92c6ec",
+          "path": "/~/ep1-example-directory/"
+        },
+        "intermediate": {
+          "id": "ddb59af0-6d04-11e5-ba46-22000b92c6ec",
+          "path": "/~/ep2-intermediate-directory/"
+        },
+        "destination__": {
+          "id": "ddb59aef-6d04-11e5-ba46-22000b92c6ec",
+          "path": "/~/ep1-duplicate-example-directory/"
+        }
+        "transfer1_label": "This value will be used as a label for the Globus Transfer Task to copy data from the source collection to the intermediate collection",
+        "transfer2_label": "This value will be used as a label for the Globus Transfer Task to copy data from the intermediate collection to the destination collection"
     }
 
 .. _example-flow-transfer-set-permissions:
 
-"Transfer Set Permissions" Flow
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+"Transfer Set Permissions (Globus Example)"
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Flow ID: ``cdcd6d1a-b1c3-4e0b-8d4c-f205c16bf80c``.
 

docs/source/overview.rst

@@ -46,7 +46,7 @@ service. Access to ``Action Providers`` and their invocation is controlled via
 ``Globus Auth``. Some of these services may be *synchronous* meaning that an
 invocation will complete in the context of the HTTP request that triggered it.
 Other services support *asynchronous* activities, meaning that the invocation
-will persist beyond the HTTP request that invoked it and the the caller must
+will persist beyond the HTTP request that invoked it and the caller must
 monitor the ``Action`` for updates on when it is completed and its result.
 
 Globus operates a series of these ``Action Providers`` available for

docs/source/using_the_cli.rst

@@ -29,7 +29,7 @@ useful for reusing tokens, debugging purposes, or for getting more familiar with
 the Globus Automate services' APIs.
 
 Each command also supports a ``--help`` option which provides concise
-information on the the command and documents its expected inputs.
+information on the command and documents its expected inputs.
 
 In almost all cases, the output from each command will be in JSON format. The
 CLI will format the output to try to improve readability, however, you may
@@ -163,7 +163,7 @@ introspect operation to get a description of the ``Action Provider``:
     </details>
 
 From this introspection response we can see that the *scope string* for
-this ``Action Provider`` is the the value of the ``globus_auth_scope`` field,
+this ``Action Provider`` is the value of the ``globus_auth_scope`` field,
 ``https://auth.globus.org/scopes/actions.globus.org/hello_world``. We
 can also see that the ``admin_contact`` is Globus.
 
@@ -514,7 +514,7 @@ view the Flow and only they will be able to run an instance of the Flow. When
 deploying, it's possible to specify who should be able to see and run the Flow.
 Using the ``visible_to`` flag, you can indicate which Globus identities can view
 the deployed Flow, or set it to ``public``, which creates a Flow viewable by
-anyone. Using the ``runnable_by`` flag, you can indicate which Globus ideneties
+anyone. Using the ``runnable_by`` flag, you can indicate which Globus identities
 can run an instance of the deployed Flow, or set a value of
 ``all_authenticated_users`` which allows any authenticated user to run an
 instance of the Flow.