Repository navigation
Open
Labels
area/testsuiteTest suites — flaky/failing tests, CI test config, test migrationTest suites — flaky/failing tests, CI test config, test migrationkind/enhancementCategorizes a PR related to an enhancementCategorizes a PR related to an enhancementstatus/labeled-by-botIssue type or area was assigned automatically by the triage botIssue type or area was assigned automatically by the triage botstatus/triageteam/continuous-deliveryteam/core-iam
Milestone
Description
Description
Current testing around LDAP is far from great; in GitHub Actions we are using the no longer maintained Apache DS embedded LDAP server, we have issues with the internal pipelines that tests with other vendors, and Dev UX is far from good when working on and testing around LDAP.
Value Proposition
Improve testing and developer UX around LDAP
Goals
- Speed and not take too much time to run tests
- Make it easier to switch between vendors when running a test
- Make it easier to import entries to ldap
- Make it easier to manage entries in ldap
- Allow running multiple LDAP servers for a single test
Non-Goals
- Migrate existing LDAP tests
Discussion
No response
Notes
LDAP tests should most likely be moved to a separate test bundle (tests/ldap) and introduce an LDAP supplier. We should have providers for those LDAP vendors that can be containerized, for others we should support remotely connecting like we do for DBs.
Metadata
Metadata
Assignees
Labels
area/testsuiteTest suites — flaky/failing tests, CI test config, test migrationTest suites — flaky/failing tests, CI test config, test migrationkind/enhancementCategorizes a PR related to an enhancementCategorizes a PR related to an enhancementstatus/labeled-by-botIssue type or area was assigned automatically by the triage botIssue type or area was assigned automatically by the triage botstatus/triageteam/continuous-deliveryteam/core-iam
Type
Fields
V 4C2D alue
None yet
Effort
None yet
Votes
None yet
Projects
- StatusShow more project fieldsOpen
Activity