VAULT-35602: Adding Enos OpenLDAP test#30801
Conversation
|
CI Results: |
|
Build Results: |
b9108e4 to
10d75cb
Compare
114972c to
01fd627
Compare
2cf40b3 to
b3a7b83
Compare
b3a7b83 to
c8c003f
Compare
ryancragun
left a comment
There was a problem hiding this comment.
I'm excited to get this in ASAP! A few mostly naming related bits of feedback.
61a3701 to
1746120
Compare
ryancragun
left a comment
There was a problem hiding this comment.
This is looking pretty close. I definitely don't want to expose SSH on the integration machines to all addresses, so that will have to be resolved before we merge. I put most of my scenario based feedback on the agent scenario but it applies to all scenarios.
ryancragun
left a comment
There was a problem hiding this comment.
Looking good! Just a few more tweaks and a couple of DRY improvements and I think this is ready. When the rest of the feedback is addressed it'd be good to do a test run of this branch in enterprise to ensure we haven't regressed somewhere.
|
tested change on enterprise and all tests passed: |
ryancragun
left a comment
There was a problem hiding this comment.
Looks good! Let's just do that rename and merge this.
Description
VAULT-35602: Adding Enos OpenLDAP test
TODO only if you're a HashiCorp employee
backport/label that matches the desired release branch. Note that in the CE repo, the latest release branch will look likebackport/x.x.x, but older release branches will bebackport/ent/x.x.x+ent.of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.