Skip to content

[WIP] fix: Inject ldap implicitly to the settings loader #725

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

Draft
wants to merge 1 commit into
base: devel
Choose a base branch
from

Conversation

rochacbruno
Copy link
Member

File "/etc/tower/conf.d/ldap.py", line 2, in <module>
ldap.OPT_X_TLS_REQUIRE_CERT: True,
^^^^
NameError: name 'ldap' is not defined

NO_JIRA

```
File "/etc/tower/conf.d/ldap.py", line 2, in <module>
ldap.OPT_X_TLS_REQUIRE_CERT: True,
^^^^
NameError: name 'ldap' is not defined
```
Copy link

github-actions bot commented May 9, 2025

DVCS PR Check Results:

Could not find JIRA key(s) in PR title, branch name, or commit messages

Copy link

sonarqubecloud bot commented May 9, 2025

@AlanCoding
Copy link
Member

I'll be honest that I like ansible/awx-operator#2043 a million times better than this

@john-westcott-iv john-westcott-iv changed the title fix: Inject ldap implicitly to the settings loader [WIP] fix: Inject ldap implicitly to the settings loader May 21, 2025
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