Skip to content
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

1password - fix system test preserve_original_event #11554

Merged

Conversation

andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Oct 28, 2024

Proposed commit message

The system tests for 1password place the preserve_original_event
configuration option into the the top-level vars instead of the
per data_stream vars where the variable is declared. The sample
events generated by the system tests did not contain the
'event.original' field as a result.

The system tests for 1password place the preserve_original_event
configuration option into the the top-level vars instead of the
per data_stream vars where the variable is declared. The sample
events generated by the system tests did not contain the
'event.original' field as a result.
[git-generate]
elastic-package -C packages/1password test system -g
elastic-package -C packages/1password build
@andrewkroh andrewkroh force-pushed the 1password/bugfix/sample-event-original branch from c6df340 to 2dc48fc Compare October 28, 2024 20:52
@elasticmachine
Copy link

💚 Build Succeeded

@andrewkroh andrewkroh marked this pull request as ready for review October 28, 2024 21:40
@andrewkroh andrewkroh requested a review from a team as a code owner October 28, 2024 21:40
@andrewkroh andrewkroh added the Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations] label Oct 28, 2024
@elasticmachine
Copy link

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

Copy link
Contributor

@efd6 efd6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ISTM that this should be something that's caught by ep.

@andrewkroh
Copy link
Member Author

The fact that this is accepted probably means the POST /api/fleet/package_policies fleet API is not strict about validating the specified parameters exist.

It is something that elastic-package could validate. Surprisingly, there are only two levels of variables listed in the code1 when there are four levels of specifying variables in packages (integration, policy template, policy template input, data stream). I'll open an issue.

Footnotes

  1. https://github.com/elastic/elastic-package/blob/700dd69a9df381475fbdc3440d01db093ec233f9/internal/testrunner/runners/policy/testconfig.go#L20-L23

@andrewkroh
Copy link
Member Author

@andrewkroh andrewkroh merged commit 66e9b4b into elastic:main Oct 28, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Integration:1password 1Password Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants