Globus-automate-client

Latest version: v0.17.1

Safety actively analyzes 630406 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

0.12.0

Not secure
===================

Features
--------

- CLI and SDK support for updating user roles on new and existing Runs
- Wherever identities are referenced on the CLI we now support supplying Globus Auth usernames instead.
- Updates to CLI and SDK arguments to more closely reflect RBAC updates in the Flows service.

Bugfixes
--------

- The Run enumeration CLI and SDK methods would attempt to use the Flow manage authorizer to authenticate its calls.
This method has been updated to instead look up or create an authorizer for the RUN_STATUS scope

Documentation
-------------

- The RBAC system for the Flows service has been updated to follow a subset model
rather than the previously existing separate permissions model.
The documentation has been updated with `a description of the new behavior <https://globus-automate-client.readthedocs.io/en/latest/overview.html?highlight=role#authentication-and-authorization>`_.

0.11.5

Not secure
===================

Features
--------

- Adds SDK and CLI support for dry running a Flow deploy or Flow run
- Adds SDK + CLI commands for enumerating Actions and sorting/filtering through results
- Adds a CLI command to retrieve a single Flow definition and its metadata: ``globus-automate flow get <id>``
- Expands the use of the ``create_flows_client`` function to allow specifying an authorizer, an authorizer callback, and a http_timeout.

Bugfixes
--------

- Fixes a regression where Flow deploy results via the CLI were unformatted
- Adds license to output of ``pip show globus-automate-client``

Documentation
-------------

- Fixes an issue where ``FlowsClient`` and ``ActionClient`` auto-generated docs were not getting generated
- Adds references to exemplar Flows and their inputs
- Adds input examples to Action Provider reference page
- Adds a hosted CLI reference

0.11.4

Not secure
===================

Features
--------

- The CLI and SDK now allow Subscription IDs to be associated with Flows

Bugfixes
--------

- The Flow List CLI and SDK operations were sending malformed query arguments to the API,
which produced incorrect results when trying to filter based on role.
This release corrects the behavior.

0.11.3

Not secure
===================

Bugfixes
--------

- Reformats verbose output to make the separation between request information and request results more obvious
- Verbose output writes output to ``stderr`` to allow output to be parsed as ``JSON``
- Empty query arguments are not sent as part of the Flows API request

Documentation
-------------

- Typo fixes

0.11.1

Not secure
===================

Features
--------

- ``flow display`` can now visualize local Flow definitions and deployed Flows.

Bugfixes
--------

- Fixes an issue where the Globus Auth login link was being rendered as a non-clickable link.
- Fixes an issue where the prompt for inputting the Globus Auth auth code was disappearing.

Documentation
-------------

- Adds explanation and examples for how to use ``manage_by`` and ``monitor_by`` values on Actions and Flow runs to delegate access to other identities.
- Clarifies the expected format for provided identities.
- Explicitly adds ``manage_by`` and ``monitor_by`` as parameters to the ``FlowsClient.run`` method.

0.11.0

===================

Features
--------

- Export the ``validate_flow_definition`` function which can be used to perform a local JSONSchema based validation of a Flow definition.
- Using ``create_flows_client`` no longer requires the use of a ``CLIENT_ID``.
- The ``action run``, ``action status``, ``flow run``, ``flow status``, and ``flow log`` CLI commands
implement a new ``--watch`` flag which lets you stream an Action's status updates.
- CLI and SDK level support for filtering and ordering Flow Listing and Flow Action Enumerations endpoints [preview].
- New CLI commands to facilitate the following ``Globus Auth`` operations:
- ``session whoami`` - determine the caller's user information as it exists in Auth
- ``session logout`` - remove locally cached auth state
- ``session revoke`` - invalidate local tokens and remove locally cached auth state.

Documentation
-------------

- Various typo fixes.

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.