Open
Conversation
Closed
Member
|
Thanks @gbonnefille ! See my comments in #252. I have to think and decide where to go next. |
Contributor
Author
|
Any news on this topic? |
Signed-off-by: Guilhem Bonnefille <guilhem.bonnefille@csgroup.eu>
gbonnefille
force-pushed
the
use-ldap-api
branch
from
83b525c to
9c057e6
Compare
|
Anyone to review and merge this? There seems to be fix for skipping LDAP re-creation if it is already there and there are dependecies on it preventing its removal. |
Member
|
This is currently being reworked on a personal branch and should be part of the next major version with more switches from groovy to api. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
An other example of conversion to API.
Could be helpful to design the definitive solution.
See #252