-
Notifications
You must be signed in to change notification settings - Fork 24
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
Remove LDAP that was deprecated last commit #265
Remove LDAP that was deprecated last commit #265
Conversation
e27b32d
to
b91e701
Compare
I assume this means we can now remove LDAP as a requirement from these places: |
Yes, that should be correct. I'll get rid of them, next. |
Anything I've missed? |
The [broker] section of the two configs could do with tidying up. |
What happens at https://github.com/apel/ssm/pull/265/files#diff-24d78e07bee2eb3c5108ab36194eba3f8765c8c6b86da792ac2b1a87447dc4b6L180-L184 now that Does the SSM just refuse to run because @tofu-rocketry, does this change negate apel/apel#40 ? |
I may be missing something but I don't think there's a non exiting case in stomp SSL where brokers will ever be 0 if host and port has been set correctly |
Yes, you're right - I'm being silly. |
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.
All that beautiful code lost, like tears in rain. 🥲
22e8713
to
5159e1d
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.
Just went through the requested changes: everything was done though I needed to add back the changelog tag
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.
Bit about installing LDAP in the README needs removing.
my first PR to this repository, ready! a PR to destroy so much LDAP! my eyes are getting misty :,) |
Thanks for doing that fix! I wasn't expecting you to do it personally. |
One less headache, aye? ship it!
…On Thu, 9 May 2024, 14:04 Adrian Coveney, ***@***.***> wrote:
my first PR to this repository, ready! a PR to destroy so much LDAP! my
eyes are getting misty :,)
Thanks for doing that fix! I wasn't expecting you to do it personally.
—
Reply to this email directly, view it on GitHub
<#265 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU3PGZ4YBQUAMOQ3YVX64XLZBNX65AVCNFSM6AAAAAA442N5UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSGYZDCMZVGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
29c1c28
to
b8bd4c6
Compare
Deprecation of LDAP requires removal of brokers.py, test_brokers.py and modifications to agent.py which this commit does.
b8bd4c6
to
3dbd30d
Compare
Also update comment to remove no-long applicable reference.
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.
LGTM
Resolves #225
Resolves GT-215
Goodbye, LDAP. Hello, new world! This pull request cleanly exorcises LDAP from our codebase, leaving the only mark of its passing the mention of a BDII in the setup/config files.