fix(elasticsearch): add compression to Elasticsearch output generation

[vparfonov]

Description

/cc @Clee2691
/assign @jcantrill

Links

• Depending on PR(s):
• GitHub issue:
• JIRA: https://redhat.atlassian.net/browse/LOG-9634
• Enhancement proposal:

Summary by CodeRabbit

• New Features

  • Elasticsearch output now respects compression settings, including gzip, when generating sink configuration.
  • Added support for generated Elasticsearch configuration with tuning plus compression enabled.

• Tests

  • Expanded coverage for Elasticsearch output generation to verify the new compression-enabled configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Elasticsearch output generator now explicitly sets the sink's Compression field from the tuning configuration. A new test case with an expected TOML fixture verifies gzip compression is correctly applied alongside existing tuning settings.

Changes

Elasticsearch Compression Configuration

Layer / File(s)	Summary
Sink compression wiring and test verification internal/generator/vector/output/elasticsearch/elasticsearch.go, internal/generator/vector/output/elasticsearch/elasticsearch_test.go, internal/generator/vector/output/elasticsearch/es_with_tune_and_compression.toml	Sets s.Compression from o.GetTuning().Compression in the sink constructor, adds a new test case with Compression: "gzip" and tlsSpec, and adds the expected generated TOML fixture with a remap transform and full elasticsearch sink configuration.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested labels: lgtm

Suggested reviewers: cahartma

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description has the required sections and commands, but it lacks a real summary of the change and most link fields are empty.	Add a concise implementation/context summary and fill in the related PR, issue, or proposal links.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: adding compression to Elasticsearch output generation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@internal/generator/vector/output/elasticsearch/elasticsearch.go`:
- Line 41: Elasticsearch tuning validation is too permissive because
ElasticsearchTuningSpec.Compression can be set to a value that Vector’s
Elasticsearch sink does not support. Update the Elasticsearch generator path in
the Elasticsearch output code, especially the logic that assigns s.Compression
in the Elasticsearch sink builder, so only none and gzip are accepted and any
other compression value is rejected or mapped before rendering. Ensure the
validation matches the sink’s supported CompressionType values and prevents
invalid compression from reaching the rendered configuration.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 8bebac39-9e07-4833-bbda-3af1c3543cd9

📥 Commits

Reviewing files that changed from the base of the PR and between bd1f2f4 and 23037e9.

📒 Files selected for processing (3)

• internal/generator/vector/output/elasticsearch/elasticsearch.go
• internal/generator/vector/output/elasticsearch/elasticsearch_test.go
• internal/generator/vector/output/elasticsearch/es_with_tune_and_compression.toml

[vparfonov]

/assign @jcantrill

[jcantrill]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill, vparfonov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jcantrill]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@vparfonov: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-using-bundle	23037e9	link	false	/test e2e-using-bundle

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.