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.

Sign up for GitHub

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

Jump to bottom

[System test runner] Allow input selection from config.yml #186

Closed
andrewkroh opened this issue Nov 25, 2020 · 1 comment · Fixed by #187
Closed

[System test runner] Allow input selection from config.yml #186

andrewkroh opened this issue Nov 25, 2020 · 1 comment · Fixed by #187
Labels
enhancement New feature or request

Comments

@andrewkroh
Copy link
Member

For data streams that have multiple input options (example) in their manifest.yml, I would like a way to select the stream under test via the test's config.yml.

Perhaps allowing the input type to be specified from the config.yml would address this? Currently the system test runner always enables the first stream in the list.

input: logfile
vars: ~
data_stream:
  vars:
    paths:
      - "{{SERVICE_LOGS_DIR}}/*.log"
@andrewkroh andrewkroh added the enhancement New feature or request label Nov 25, 2020
andrewkroh added a commit to andrewkroh/integrations that referenced this issue Nov 25, 2020
@andrewkroh
Add system test for Cisco IOS
2b47405 
A system test was required because all of the parsing logic lives on the agent
side rather than in an ingest pipeline. The tests detected several missing fields.

In order to test the logfile input (instead of the syslog input) a solution to elastic/elastic-package#186
is required.
@andrewkroh andrewkroh mentioned this issue Nov 25, 2020
Merged
2 tasks
andrewkroh added a commit to andrewkroh/elastic-package that referenced this issue Nov 25, 2020
@andrewkroh
Add a way to select the stream under test in system test runner
fb7fda0 
This provides a means to select a stream to test by input type.

Closes elastic#186
@andrewkroh andrewkroh mentioned this issue Nov 25, 2020
Merged
@andrewkroh
Copy link
Member Author

I opened #187 which provides a way to select based on the input type. Another option would be to simply specify the stream index directly.

andrewkroh added a commit that referenced this issue Dec 1, 2020
@andrewkroh
Add a way to select the stream under test in system test runner (#187)
4a022f5 
This provides a means to select a stream to test by input type.

Closes #186
andrewkroh added a commit to andrewkroh/integrations that referenced this issue Dec 1, 2020
@andrewkroh
Add system test for Cisco IOS
a750f9a 
A system test was required because all of the parsing logic lives on the agent
side rather than in an ingest pipeline. The tests detected several missing fields.

In order to test the logfile input (instead of the syslog input) a solution to elastic/elastic-package#186
is required.
andrewkroh added a commit to andrewkroh/integrations that referenced this issue Dec 1, 2020
@andrewkroh
Add system test for Cisco IOS
2ddaeb7 
A system test was required because all of the parsing logic lives on the agent
side rather than in an ingest pipeline. The tests detected several missing fields.

In order to test the logfile input (instead of the syslog input) a solution to elastic/elastic-package#186
is required.
andrewkroh added a commit to elastic/integrations that referenced this issue Dec 2, 2020
@andrewkroh
Add system test for Cisco IOS (#416)
45a68f9 
A system test was required because all of the parsing logic lives on the agent
side rather than in an ingest pipeline. The tests detected several missing fields.

In order to test the logfile input (instead of the syslog input) a solution to elastic/elastic-package#186
is required.
eyalkraft pushed a commit to build-security/integrations that referenced this issue Mar 30, 2022
@andrewkroh
Add system test for Cisco IOS (elastic#416)
c80213f 
A system test was required because all of the parsing logic lives on the agent
side rather than in an ingest pipeline. The tests detected several missing fields.

In order to test the logfile input (instead of the syslog input) a solution to elastic/elastic-package#186
is required.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a way to select the stream under test in system test runner andrewkroh/elastic-package
1 participant
@andrewkroh