Bump globus-sdk from 3.44.0 to 3.45.0

[dependabot[bot]]

Bumps globus-sdk from 3.44.0 to 3.45.0.

Release notes

Sourced from globus-sdk's releases.

v3.45.0

Added

• The scope builder for SpecificFlowClient is now available for direct access and use via globus_sdk.scopes.SpecificFlowScopeBuilder. Callers can initialize this class with a flow_id to get a scope builder for a specific flow, e.g., SpecificFlowScopeBuilder(flow_id).user. SpecificFlowClient now uses this class internally. (#1030)

• TransferClient.add_app_data_access_scope now accepts iterables of collection IDs as an alternative to individual collection IDs. (#1034)

Experimental

• Added login(...), logout(...), and login_required(...) to the experimental GlobusApp construct. (#1041)

  • login(...) initiates a login flow if:

    • the current entity requires a login to satisfy local scope requirements or
    • auth_params/force=True is passed to the method.

  • logout(...) remove and revokes the current entity's app-associated tokens.

  • login_required(...) returns a boolean indicating whether the app believes a login is required to satisfy local scope requirements.

Removed

Experimental

• Made run_login_flow private in the experimental GlobusApp construct. Usage sites should be replaced with either app.login() or app.login(force=True). (#1041)

  • Old Usage

    app = UserApp("my-app", client_id="<my-client-id>")
    app.run_login_flow()
    

  • New Usage

    app = UserApp("my-app", client_id="<my-client-id>")
    app.login(force=True)
    

Changed

• The client for Globus Timers has been renamed to TimersClient. The prior name, TimerClient, has been retained as an alias. (#1032)

  • Similarly, the error and scopes classes have been renamed and aliased: TimersAPIError replaces TimerAPIError and TimersScopes replaces TimerScopes.

  • Internal module names have been changed to timers from timer where possible.

  • The service_name attribute is left as timer for now, as it is integrated into URL and _testing logic.

... (truncated)

Changelog

Sourced from globus-sdk's changelog.

v3.45.0 (2024-09-06)

Added

- The scope builder for ``SpecificFlowClient`` is now available for direct
  access and use via ``globus_sdk.scopes.SpecificFlowScopeBuilder``. Callers can
  initialize this class with a ``flow_id`` to get a scope builder for a
  specific flow, e.g., ``SpecificFlowScopeBuilder(flow_id).user``.
  ``SpecificFlowClient`` now uses this class internally. (:pr:`1030`)

TransferClient.add_app_data_access_scope now accepts iterables of

collection IDs as an alternative to individual collection IDs. (:pr:1034)

.. rubric:: Experimental


Added login(...), logout(...), and login_required(...) to the

experimental GlobusApp construct. (:pr:1041)


login(...) initiates a login flow if:

the current entity requires a login to satisfy local scope requirements or
auth_params/force=True is passed to the method.



logout(...) remove and revokes the current entity's app-associated tokens.


login_required(...) returns a boolean indicating whether the app believes

a login is required to satisfy local scope requirements.




Removed

.. rubric:: Experimental

• Made run_login_flow private in the experimental GlobusApp construct. Usage sites should be replaced with either app.login() or app.login(force=True). (:pr:1041)

  • Old Usage

    .. code-block:: python

    app = UserApp("my-app", client_id="<my-client-id>")
    app.run_login_flow()
    

  • New Usage

    .. code-block:: python

... (truncated)

Commits

• c99a4a5 Bump version and changelog for release (#1043)
• f7ddd1d (actions) update PR references
• ca3bb36 GlobusApp login, logout, and login_required (#1041)
• 028e502 (actions) update PR references
• 898bd79 Replace app requirement exploration method (#1042)
• a121aa3 (actions) update PR references
• e960e09 Allow better customization of CLI LoginFlowManager (#1039)
• b406d3f (actions) update PR references
• 7b16f7a Make GlobusApp.token_storage public (#1040)
• ec38659 (actions) update PR references
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)