-
Notifications
You must be signed in to change notification settings - Fork 0
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
test: Support single-source sync #80
Conversation
As mentioned in the original PR in this comment, we first need to clarify how to approach the clash between LDAP and CSV sync. Then a small adjustment to the |
045ea82
to
a4ec83e
Compare
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.
Looks good, I like this!
@@ -19,6 +19,7 @@ feature_flags: | |||
# - deactivate_only # Only deactivate users, do not create or update them. Keep in mind LDAP is cached and all the changes made on LDAP will be written to the cache as if they where applied. Therefore, only the deactivation changes will be applied to Zitadel but **all the other changes will be lost**. | |||
|
|||
# Configuration for the sources to sync from. | |||
# IMPORTANT: Only one source can be present at a time. |
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.
I think the sample config should be split in three for this, don't want to document something that can never work.
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.
Okay, let's split the sample as part of the documentation commit on the feature branch.
Closes: #81
This fixes tests for: #79
As per this comment.