Keep track of which groups are possibleToDelete #31002
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add an attribute of a group
possibleToDelete
which isfalse
for LDAP groups. Use that attribute to decide what sort of group existence... checks we should really enforce.LDAP users actually can be deleted on the local ownCloud, so remove the
$shouldExist = false
setting from those. We are happy forAfterScenario
code to get rid of those users (which it is doing now) and to give warnings if it cannot.This should help acceptance tests in
user_ldap
Related Issue
Motivation and Context
When running user_ldap tests, the
AfterScenario
that cleans up groups complains because it cannot delete the LDAP groups. That is because there is a:that double-checks that the group really is gone, after attempting to delete it.
For LDAP, actually the group(s) cannot be deleted. so that double-check is not relevant in that case. For LDAP groups we are forced to just keep going between scenarios without explicitly deleting all the groups and creating them again.
How Has This Been Tested?
CI knows
Types of changes
Checklist: