From a499a499df7273bbae143b5343327a9f437a8840 Mon Sep 17 00:00:00 2001 From: Reid Mello <30907815+rjmello@users.noreply.github.com> Date: Thu, 20 Jun 2024 10:07:55 -0400 Subject: [PATCH] Bump versions and changelog for release v2.22.0 --- ...423_142117_yadudoc1729_gce_working_dir.rst | 40 ------------- ...0320_chris_document_443_default_switch.rst | 6 -- ..._enable_configurable_interchange_debug.rst | 8 --- .../globus_compute_endpoint/version.py | 2 +- compute_endpoint/setup.py | 2 +- compute_sdk/globus_compute_sdk/version.py | 2 +- docs/changelog.rst | 58 +++++++++++++++++++ 7 files changed, 61 insertions(+), 57 deletions(-) delete mode 100644 changelog.d/20240423_142117_yadudoc1729_gce_working_dir.rst delete mode 100644 changelog.d/20240604_170320_chris_document_443_default_switch.rst delete mode 100644 changelog.d/20240612_164858_kevin_enable_configurable_interchange_debug.rst diff --git a/changelog.d/20240423_142117_yadudoc1729_gce_working_dir.rst b/changelog.d/20240423_142117_yadudoc1729_gce_working_dir.rst deleted file mode 100644 index c3372ccaa..000000000 --- a/changelog.d/20240423_142117_yadudoc1729_gce_working_dir.rst +++ /dev/null @@ -1,40 +0,0 @@ -New Functionality -^^^^^^^^^^^^^^^^^ - -- ``GlobusComputeEngine`` now supports a ``working_dir`` keyword argument that sets the directory in which - all functions will be executed. Relative paths, if set, will be considered relative to the endpoint directory - (``~/.globus_compute/``). If this option is not set, ``GlobusComputeEngine`` will use the - endpoint directory as the working directory. Set this option using ``working_dir: `` - Example config: - - .. code-block:: yaml - - display_name: WorkingDirExample - engine: - type: GlobusComputeEngine - # Run functions in ~/.globus_compute//TASKS - working_dir: TASKS - -- ``GlobusComputeEngine`` now supports function sandboxing, where each function is executed within a - sandbox directory for better isolation. When this option is enabled by setting ``run_in_sandbox: True`` - a new directory with the function UUID as the name is created in the working directory (configurable with - the ``working_dir`` kwarg). Example config: - - .. code-block:: yaml - - display_name: WorkingDirExample - engine: - type: GlobusComputeEngine - # Set working dir to /projects/MY_PROJ - working_dir: /projects/MY_PROJ - # Enable sandboxing to have functions run under /projects/MY_PROJ// - run_in_sandbox: True - - -Bug Fixes -^^^^^^^^^ - -- Fixed bug where ``GlobusComputeEngine`` set the current working directory to the directory - from which the endpoint was started. Now, ``GlobusComputeEngine`` will set the working directory - to the endpoint directory (``~/.globus_compute/``) by default. This can be configured - via the endpoint config. \ No newline at end of file diff --git a/changelog.d/20240604_170320_chris_document_443_default_switch.rst b/changelog.d/20240604_170320_chris_document_443_default_switch.rst deleted file mode 100644 index 2008b041c..000000000 --- a/changelog.d/20240604_170320_chris_document_443_default_switch.rst +++ /dev/null @@ -1,6 +0,0 @@ -Changed -^^^^^^^ - -- Updated the Compute hosted services to use AMQP over port 443 by default, instead of - the standard 5671. This can still be overridden in both the SDK and the Endpoint via - ``amqp_port``. diff --git a/changelog.d/20240612_164858_kevin_enable_configurable_interchange_debug.rst b/changelog.d/20240612_164858_kevin_enable_configurable_interchange_debug.rst deleted file mode 100644 index f657fa491..000000000 --- a/changelog.d/20240612_164858_kevin_enable_configurable_interchange_debug.rst +++ /dev/null @@ -1,8 +0,0 @@ -New Functionality -^^^^^^^^^^^^^^^^^ - -- Implement ``debug`` as a top-level config boolean for a Compute Endpoint. - This flag determines whether debug-level logs are emitted -- the same - functionality as the ``--debug`` command line argument to the - ``globus-compute-endpoint`` executable. Note: if this flag is set to - ``False`` when the ``--debug`` CLI flag is specified, the CLI wins. diff --git a/compute_endpoint/globus_compute_endpoint/version.py b/compute_endpoint/globus_compute_endpoint/version.py index b22cbd9f6..e9da77694 100644 --- a/compute_endpoint/globus_compute_endpoint/version.py +++ b/compute_endpoint/globus_compute_endpoint/version.py @@ -1,6 +1,6 @@ # single source of truth for package version, # see https://packaging.python.org/en/latest/single_source_version/ -__version__ = "2.22.0a0" +__version__ = "2.22.0" # TODO: remove after a `globus-compute-sdk` release # this is needed because it's imported by `globus-compute-sdk` to do the version check diff --git a/compute_endpoint/setup.py b/compute_endpoint/setup.py index ac22ae0aa..0118ded1d 100644 --- a/compute_endpoint/setup.py +++ b/compute_endpoint/setup.py @@ -6,7 +6,7 @@ REQUIRES = [ "requests>=2.31.0,<3", "globus-sdk", # version will be bounded by `globus-compute-sdk` - "globus-compute-sdk==2.22.0a0", + "globus-compute-sdk==2.22.0", "globus-compute-common==0.4.1", "globus-identity-mapping==0.3.0", # table printing used in list-endpoints diff --git a/compute_sdk/globus_compute_sdk/version.py b/compute_sdk/globus_compute_sdk/version.py index c917c22cf..3cd0e6d4e 100644 --- a/compute_sdk/globus_compute_sdk/version.py +++ b/compute_sdk/globus_compute_sdk/version.py @@ -3,7 +3,7 @@ # single source of truth for package version, # see https://packaging.python.org/en/latest/single_source_version/ -__version__ = "2.22.0a0" +__version__ = "2.22.0" def compare_versions( diff --git a/docs/changelog.rst b/docs/changelog.rst index 3732776a3..9fa157b11 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -3,6 +3,64 @@ Changelog .. scriv-insert-here +.. _changelog-2.22.0: + +globus-compute-sdk & globus-compute-endpoint v2.22.0 +---------------------------------------------------- + +New Functionality +^^^^^^^^^^^^^^^^^ + +- ``GlobusComputeEngine`` now supports a ``working_dir`` keyword argument that sets the directory in which + all functions will be executed. Relative paths, if set, will be considered relative to the endpoint directory + (``~/.globus_compute/``). If this option is not set, ``GlobusComputeEngine`` will use the + endpoint directory as the working directory. Set this option using ``working_dir: `` + Example config: + + .. code-block:: yaml + + display_name: WorkingDirExample + engine: + type: GlobusComputeEngine + # Run functions in ~/.globus_compute//TASKS + working_dir: TASKS + +- ``GlobusComputeEngine`` now supports function sandboxing, where each function is executed within a + sandbox directory for better isolation. When this option is enabled by setting ``run_in_sandbox: True`` + a new directory with the function UUID as the name is created in the working directory (configurable with + the ``working_dir`` kwarg). Example config: + + .. code-block:: yaml + + display_name: WorkingDirExample + engine: + type: GlobusComputeEngine + # Set working dir to /projects/MY_PROJ + working_dir: /projects/MY_PROJ + # Enable sandboxing to have functions run under /projects/MY_PROJ// + run_in_sandbox: True + +- Implement ``debug`` as a top-level config boolean for a Compute Endpoint. + This flag determines whether debug-level logs are emitted -- the same + functionality as the ``--debug`` command line argument to the + ``globus-compute-endpoint`` executable. Note: if this flag is set to + ``False`` when the ``--debug`` CLI flag is specified, the CLI wins. + +Bug Fixes +^^^^^^^^^ + +- Fixed bug where ``GlobusComputeEngine`` set the current working directory to the directory + from which the endpoint was started. Now, ``GlobusComputeEngine`` will set the working directory + to the endpoint directory (``~/.globus_compute/``) by default. This can be configured + via the endpoint config. + +Changed +^^^^^^^ + +- Updated the Compute hosted services to use AMQP over port 443 by default, instead of + the standard 5671. This can still be overridden in both the SDK and the Endpoint via + ``amqp_port``. + .. _changelog-2.21.0: globus-compute-sdk & globus-compute-endpoint v2.21.0