remove duplicate placeholder in sample config

[jpinsonneau]

Description

Fix sample

Dependencies

n/a

Checklist

• Does the changes in PR need specific configuration or environment set up for testing?
  • if so please describe it in PR description.
• I have added thorough unit tests for the change.
• QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

• Chores
  • Removed duplicate configuration entry in the DNS flag response code filter to streamline settings.

[coderabbitai]

📝 Walkthrough

Walkthrough

A duplicate placeholder configuration line was removed from the sample YAML config file, leaving a single placeholder value for the DNS flag response code filter.

Changes

Cohort / File(s)	Summary
Configuration config/sample-config.yaml	Removed duplicate frontend.filters[id: dns_flag_response_code].placeholder entry, retaining one placeholder value ('E.g: NoError, NXDomain, NotAuth').

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is too vague. 'Fix sample' provides no meaningful context about what was fixed or why.	Expand the Description section to explain what issue was fixed and why the duplicate placeholder needed removal.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately summarizes the main change: removing a duplicate placeholder line from the sample config file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[jotak]

LGTM
But I just ran the provided script to update this config, so is it that it's also wrong on the operator side?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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:

• DOWNSTREAM_OWNERS

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

[jpinsonneau]

LGTM But I just ran the provided script to update this config, so is it that it's also wrong on the operator side?

ok also created netobserv/netobserv-operator#2616
I took the liberty to approve it directly since it's the same changes as here