google / google/osdfir-infrastructure

Print Plaso --version integration

Open
#207 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go Template
Stars
213
Forks
30
Avg merge
14h 33m
Merged PRs (30d)
5

Description

### Name and Version

Chart Name: osdfir-infrastructure Chart Version: (found in Chart.yaml) /workspaces/osdfir-infrastructure/charts/osdfir-infrastructure/Chart.yaml

### What is the problem this feature will solve?

Currently, there is no clear indication of which Plaso version is executed during the integration tests. This lack of version visibility can hinder troubleshooting, reproducibility, and auditability, especially when test results or failures may be influenced by differences between Plaso releases. By not recording the version, it becomes challenging for maintainers and users to correlate test outcomes with specific software versions, potentially leading to confusion and inefficiencies in diagnosing issues. Introducing a mechanism to print the Plaso version at the start of the integration test script will ensure that every test run is traceable to a specific Plaso release, thereby improving transparency, reliability, and maintainability of the testing process.

### What is the feature you are proposing to solve the problem?

The proposed feature is to add a print statement at the beginning of the integration test script that displays the Plaso version being used. This will ensure that every test run records and communicates the exact Plaso release, improving traceability, reproducibility, and ease of troubleshooting for all users and maintainers.

### What alternatives have you considered?

Alternatives considered include:

Manually documenting the Plaso version used for each test run in a separate log or README file.
Using environment variables or configuration files to specify and record the Plaso version.
Implementing automated dependency/version management tools to track software versions. However, these approaches are less reliable and more error-prone compared to directly printing the version in the test script output.

Contributor guide

Open the contributing guide

Research direction

Start with the integration test script for the osdfir-infrastructure chart and review Chart.yaml at /workspaces/osdfir-infrastructure/charts/osdfir-infrastructure/Chart.yaml for the chart context. Add Plaso version output at the beginning of the script and verify that an integration-test run records it.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, testing
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.