-
Notifications
You must be signed in to change notification settings - Fork 692
chore: remove ingest.enabled config #6873
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -67,7 +67,6 @@ block_builder: | |
| - 0 | ||
|
|
||
| ingest: | ||
| enabled: true | ||
| kafka: | ||
| address: kafka:9092 | ||
| topic: tempo-ingest | ||
|
|
||
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -34,6 +34,10 @@ type Config struct { | |||||||||
| IngestStorageConfig ingest.Config `yaml:"-"` | ||||||||||
| } | ||||||||||
|
|
||||||||||
| func ingestStorageEnabled(cfg ingest.Config) bool { | ||||||||||
| return cfg.Kafka.Topic != "" | ||||||||||
|
Comment on lines
+37
to
+38
|
||||||||||
| func ingestStorageEnabled(cfg ingest.Config) bool { | |
| return cfg.Kafka.Topic != "" | |
| func ingestStorageEnabled(cfg *ingest.Config) bool { | |
| return cfg != nil && cfg.Kafka.Topic != "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just to make this thing build. Ingesters are about to disappear
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
## main / unreleasedsection now has an extra blank line between list items (line 4), and the first entry is an[ENHANCEMENT]that sits above the[CHANGE]block. Could we remove the blank line and keep entries grouped/sorted by type (CHANGE/FEATURE/ENHANCEMENT/BUGFIX) to match the checklist guidance and the rest of the file’s structure?