Skip to content
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

[LDAP-41] Provide capability for different sync strategies #20

Merged
merged 8 commits into from
Jan 19, 2024
Merged

[LDAP-41] Provide capability for different sync strategies #20

merged 8 commits into from
Jan 19, 2024

Conversation

Sylinsic
Copy link
Contributor

Currently, it is only possible to utilise the SunDSChangeLogSyncStrategy method. This is not ideal as not all companies implement changelogs in the same fashion. There should be a method to select a SyncStrategy, as is the case with the ADBundle, which is suitable for the software being connected to.

@ilgrosso
Copy link
Member

@Sylinsic please clean up this PR to include only the changes related to LDAP-41

@Sylinsic Sylinsic requested a review from ilgrosso January 19, 2024 09:14
ilgrosso
ilgrosso previously approved these changes Jan 19, 2024
@ilgrosso
Copy link
Member

@Sylinsic I've made a few more adjustments.
Going to merge as soon as GH workflow is passing.

ilgrosso
ilgrosso previously approved these changes Jan 19, 2024
@ilgrosso
Copy link
Member

@Sylinsic after merging of this PR, you will likely need to reinit your master branch from upstream.

For next PRs please start from a dedicated branch on your repo, forked off of master.

Please do not take into account the failures with JDK 17, those are being handled by #22

@ilgrosso ilgrosso merged commit 3230cf5 into Tirasa:master Jan 19, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants