Skip to content

Fix log_ingestor configuration fallback to defaults when set to null in Helm values.yaml #1881

@coderabbitai

Description

@coderabbitai

Problem

When log_ingestor: null is set in values.yaml, the Pydantic model parser falls back to default values, which leaves the log-ingestor configured even though it should be disabled.

Impact

When clpConfig.package.storage is configured as "clp" (CLP-Text, which doesn't support the log-ingestor), the configuration is deemed invalid and most Helm chart deployments won't start.

Solution

The configuration parser should explicitly handle null values for log_ingestor to prevent fallback to default values, ensuring the feature remains disabled when set to null.

References

Files Affected

  • tools/deployment/package-helm/values.yaml
  • Configuration parser/validator (likely Python Pydantic models)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions