The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
bulk_submit_import()
in the Auth$imports
path allows you to import multiple volume files or folders into a
project using a single API call.bulk_get()
in the Auth$imports
path
retrieves details about a bulk import job.bulk_submit_export()
in the Auth$exports
path enables you to export multiple project files into a volume using a
single API call.bulk_get()
in the Auth$exports
path
fetches details about a bulk export job.bulk_get()
in the Auth$files
path
retrieves details of multiple specified files, including file names and
metadata.bulk_update()
in the Auth$files
path
updates the details for multiple specified files, replacing existing
information and clearing omitted parameters.bulk_edit()
in the Auth$files
path
modifies existing information or adds new information for multiple
specified files, while preserving omitted parameters.bulk_delete()
in the Auth$files
path
deletes multiple specified files in a single API call.bulk_get()
in the Auth$tasks
path
retrieves details of multiple tasks in a single API call.prepare_items_for_bulk_import()
and
prepare_items_for_bulk_export()
. These functions are
designed to facilitate the creation of item lists for bulk import and
export operations.api()
function
to ensure compatibility with newer versions of R. The
setequal()
function has been replaced with the custom
list_eq()
function.fields
parameter in the
core api()
function to β_allβ, ensuring that all available
fields are included in the API response for each resource.async_bulk_copy()
in the Auth$files
path:
Copies multiple files and folders while preserving the folder structure.
Supports:
async_bulk_delete()
in the Auth$files
path: Deletes multiple files or folders asynchronously. Empty and
non-empty folders can be deleted.async_bulk_move()
in the Auth$files
path:
Moves multiple files and folders. Supports:
async_get_copy_job()
in the Auth$files
path: Retrieves details of an asynchronous bulk copy job.async_get_delete_job()
in the Auth$files
path: Retrieves details of an asynchronous bulk deletion job.async_get_move_job()
in the Auth$files
path: Retrieves details of an asynchronous bulk move job.async_list_file_jobs()
in the Auth$files
path: Lists all active and completed asynchronous bulk jobs initiated by
the user.Auth$apps$copy()
method, as the previous example was
outdated.Introduced support for Enterprise API actions, enabling users to manage organizational structures such as divisions and teams on the Seven Bridges Platform.
The following Enterprise API classes and methods have been added:
query()
and get()
in the
Auth$divisions
path allow listing all divisions and
retrieving a division by ID.list_teams()
lists all teams within a division.list_members()
retrieves division members, with
optional filtering by role.remove_member()
removes a member from the
division.query()
, get()
, create()
, and
delete()
in the Auth$teams
path allow managing
teams within divisions.list_members()
, add_member()
, and
remove_member()
for managing team membership.rename()
and delete()
for modifying or
removing a team.add_member_team()
and
add_member_division()
allow adding entire teams or
divisions as volume members (for users with appropriate
ADMIN
privileges).add_member_general()
,
which handles the underlying logic for adding volume members. All three
public methods β add_member()
,
add_member_team()
, and add_member_division()
β
now use add_member_general()
internally to ensure
consistency and reduce duplication.Added a new vignette Enterprise_actions.Rmd
covering
the full set of Enterprise API actions.
Updated the Files_upload_and_Volumes.Rmd
vignette to
document volume sharing with teams and divisions.
Fixed typos and refined wording across documentation and code comments for improved readability and maintainability.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.