| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This commit consists of patches automatically generated for this project on https://scrutinizer-ci.com
|
|
|
|
|
|
| |
Use sed - not replace
apply btrfs hack
|
| |
|
|\
| |
| | |
Dont set the string storage id to the numeric storage id for personal mounts
|
| | |
|
|/
|
|
| |
This commit consists of patches automatically generated for this project on https://scrutinizer-ci.com
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Adding group Db to federation tests and ldap tests
Add group DB to Test_UrlGenerator
Adding group DB to trashbin and versions tests
Adding group DB to Test_Util_CheckServer for pg
|
| |
|
| |
|
|\
| |
| | |
Improvements to external storages list rendering
|
| | |
|
|/ |
|
|\
| |
| | |
[files_external] swift tests
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Use netcat to check when the port opens, rather than an arbitrary
timeout. Hard limit of 60 seconds in case something breaks
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Prevents Strict warning when running autotest-external.sh
|
|
|
|
|
|
|
|
|
| |
When removing external storages, either system-wide or user-wide,
automatically remove the matching oc_storages and oc_filecache entries.
This can only work if the backend configuration doesn't contain any
substitution variable $user in which case the storage id cannot be
computed, so this case is ignored for now.
|
| |
|
| |
|
|
|
|
| |
Fixes #15037
|
| |
|
|
|
|
|
|
|
|
| |
StoragesService::getStorages() will check the visibility of the backend
and auth mechanism for the storage, and if either are not visible to the
user (aka disabled by admin) then the storage will be filtered out. The
original method StoragesService::getAllStorages() still exists in case
such storages need to be detected, but its use is discouraged.
|
|
|
|
|
|
| |
This reverts commit 0b97a05e7bd631d66de1c2aee115113ada8a5f63.
This reverts commit d2e3c17c0000bc0020f1ff641190452f370434de.
This reverts commit cc88c5f4b84da57c425cbdb7dc8b391b1942b503.
|
|\
| |
| | |
AmazonS3 automatic tests
|
| | |
|
|/ |
|
|\
| |
| | |
Migrate advanced external storage backends to new registration API [part 3]
|
| | |
|
| |
| |
| |
| |
| | |
Backend and auth mechanism permissions are checked on storage creation,
both for personal storages and for admin storages
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
VisibilityTrait -> PermissionsTrait
PermissionsTrait stores two sets of data, $permissions and
$allowedPermissions (analogous to $visibility and $allowedVisibility of
VisibilityTrait). Each set is a map of user type ('admin' or 'personal')
to permissions (mounting permission, create permission).
The result is that a backend can now be restricted for creation, while
still allowing it to be mounted. This is useful for deprecating backends
or auth mechanisms, preventing new storages being created, while still
allowing existing storages to be mounted.
|
| | |
|
| |
| |
| |
| |
| | |
Replace ->setDependencyCheck(callable) with a real method
checkDependencies(). A polyfill is available for legacy storages.
|
|/ |
|
|\
| |
| | |
setUserVars() should only attempt substitution with strings
|
| |
| |
| |
| |
| | |
Legacy compatibility, from the days in stable8 when checkbox boolean
values were stored as the strings 'true' and 'false'.
|
|/ |
|
|
|
|
|
| |
The same Application must be used in the settings templates and in
routes, so that any registered backends are correctly seen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following functions have been removed:
- addMountPoint()
- removeMountPoint()
- movePersonalMountPoint()
registerBackend() has been rewritten as a shim around BackendService,
allowing legacy code to interact with the new API seamlessly
addMountPoint() was already disconnected from all production code, so
this commit completes the job and removes the function itself, along
with disconnecting and removing related functions. Unit tests have
likewise been removed.
getAbsoluteMountPoints(), getSystemMountPoints() and
getPersonalMountPoints() have been rewritten to use the StoragesServices
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this, the storage class name was stored in mount.json under the
"class" parameter, and the auth mechanism class name under the
"authMechanism" parameter. This decouples the class name from the
identifier used to retrieve the backend or auth mechanism.
Now, backends/auth mechanisms have a unique identifier, which is saved in
the "backend" or "authMechanism" parameter in mount.json respectively.
An identifier is considered unique for the object it references, but the
underlying class may change (e.g. files_external gets pulled into core
and namespaces are modified).
|