-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solution] fix tests for unique policy names #118248
Conversation
@@ -139,12 +140,13 @@ export async function indexEndpointHostDocs({ | |||
|
|||
if (enrollFleet) { | |||
const { id: appliedPolicyId, name: appliedPolicyName } = hostMetadata.Endpoint.policy.applied; | |||
const uniqueAppliedPolicyName = `${appliedPolicyName}-${uuid.v4()}`; |
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.
I think ideally we do this within the data generator itself but since this is blocking us from unskipping our tests, I want to make the smallest changes possible for this PR.
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
Pinging @elastic/security-onboarding-and-lifecycle-mgt (Team:Onboarding and Lifecycle Mgt) |
) Co-authored-by: Joey F. Poon <[email protected]>
) Co-authored-by: Joey F. Poon <[email protected]>
Summary
fixes endpoint tests that were failing due to policy names not being unique. unique policies names were introduced in #115212. needs to be back-ported into
7.16
for #117380.Checklist
For maintainers