[DRIVERS-2420] Update Java workload executor in Astrolabe to support TLS secrets Created: 19/Aug/22 Updated: 08/Sep/22 Resolved: 08/Sep/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Astrolabe, Containerized Testing |
| Fix Version/s: | None |
| Type: | Task | Priority: | Unknown |
| Reporter: | Matt Dale | Assignee: | Matt Dale |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | DRIVERS-718 | ||||||||||||
| Driver Changes: | Not Needed | ||||||||||||
| Quarter: | FY23Q1 | ||||||||||||
| Description |
SummaryThe Java driver does not support the tlsCertificateKeyFile and tlsCAFile connection string parameters ( Set up a trust store for the Java driver via the workload exectuor script to allow it to connect to the Kind clusters that use test-specific TLS certs and CAs. See a guide for setting up a trust store here. MotivationWho is the affected end user?Who are the stakeholders? How does this affect the end user?Are they blocked? Are they annoyed? Are they confused? How likely is it that this problem or use case will occur?Main path? Edge case? If the problem does occur, what are the consequences and how severe are they?Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete? Is this issue urgent?Does this ticket have a required timeline? What is it? Is this ticket required by a downstream team?Needed by e.g. Atlas, Shell, Compass? Is this ticket only for tests?Does this ticket have any functional impact, or is it just test improvements? |
| Comments |
| Comment by Githook User [ 08/Sep/22 ] |
|
Author: {'name': 'Matt Dale', 'email': '9760375+matthewdale@users.noreply.github.com', 'username': 'matthewdale'}Message: |