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.

Sign up for GitHub

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

Jump to bottom

Figure out how to encode LDAPSearch objects via environment variables #474

Open
timabbott opened this issue Nov 19, 2024 · 0 comments
Open

Figure out how to encode LDAPSearch objects via environment variables #474

timabbott opened this issue Nov 19, 2024 · 0 comments
Labels
high priority

Comments

@timabbott
Copy link
Member

While we documented the MANUAL_CONFIGURATION workaround in #344, I think it might be possible to support LDAPSearch objects some other way:

  • It might be possible to figure out a string encoding of the Python code that be usefully processed, just like we do arrays/None, with custom code in entrypoint.sh.
  • We could just define a few Zulip-specific variable names for the actual arguments to the couple Zulip settings that accept an LDAPSearch object, to at least cover the most common approaches.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@timabbott