-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add support to expire outgoing federated shares #37548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
e96f6f5 to
157dd9f
Compare
Codecov Report
@@ Coverage Diff @@
## master #37548 +/- ##
=========================================
Coverage 64.66% 64.66%
- Complexity 19343 19350 +7
=========================================
Files 1279 1279
Lines 75600 75654 +54
Branches 1333 1336 +3
=========================================
+ Hits 48885 48924 +39
- Misses 26323 26336 +13
- Partials 392 394 +2
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #37548 +/- ##
=========================================
Coverage 64.75% 64.75%
- Complexity 19396 19403 +7
=========================================
Files 1285 1285
Lines 75762 75816 +54
Branches 1333 1336 +3
=========================================
+ Hits 49057 49096 +39
- Misses 26313 26326 +13
- Partials 392 394 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
micbar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@VicDeo can you do a code review? |
|
We should make some acceptance tests like what is done for expiration dates on user, group and public link shares. Should those be added here? Or merge this and make a separate isssue for the tests? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please include the acceptance tests here in that PR.
|
Assigned myself to sort out acceptance tests. |
|
assigned @swoichha for API tests and @haribhandari07 for UI tests |
7bae6e5 to
0bc7980
Compare
0bc7980 to
8d60174
Compare
|
@jvillafanez Here's an issue #37595 related to this PR |
|
Pls run: |
81c4f45 to
4bb8b4c
Compare
tests/acceptance/features/webUISharingExternal2/createFederationSharing.feature
Show resolved
Hide resolved
|
Anything left to do here? I see CI failing but I'm not sure if there is a problem with the tests or with the code... |
19294de to
d670539
Compare
|
I rebased just now. There were various conflicts and I think I sorted out the correct changes. Now I will review what is here and get it going. |
60f9155 to
743cf33
Compare
|
@phil-davis Thank you. How can we move that forward? |
d780480 to
d594159
Compare
|
Squashed into just 2 commits and rebased. IMO there is just 1 test scenario to sort out... |
d594159 to
8b5d8b5
Compare
9a6dc50 to
d2a0d53
Compare
|
@phil-davis @jvillafanez @micbar |
|
Doc ticket opened in owncloud/docs#2759 |
Description
Add support to expire federated shares the same way it was added for user and group shares.
New settings to add a default date and enforce it as maximum also included (the same way as for user and group shares)
Related Issue
https://github.com/owncloud/enterprise/issues/3969
Motivation and Context
How Has This Been Tested?
Manually tested:
Screenshots (if appropriate):
(orange bars are scrollbars, nothing to do with the page style)
We might need to review how we can deal with long sharee's names. Text is moved below, which looks bad compared with how shorter names are handled (local user shares)
Types of changes
Checklist: