|
| 1 | +package metadata |
| 2 | + |
| 3 | +releases: "0.15.2": { |
| 4 | + date: "2021-08-11" |
| 5 | + codename: "" |
| 6 | + |
| 7 | + description: """ |
| 8 | + The Vector team is pleased to announce version 0.15.2! |
| 9 | +
|
| 10 | + This release contains a fix for `vector validate` to source environment variables indicating configuration |
| 11 | + location: `VECTOR_CONFIG`, `VECTOR_CONFIG_YAML`, `VECTOR_CONFIG_JSON`, and `VECTOR_CONFIG_TOML`. |
| 12 | +
|
| 13 | + In v0.15.0, we released a change the SystemD unit file to run `vector validate` before start-up as part of |
| 14 | + `ExecStartPre`. If users were using, for example, `VECTOR_CONFIG` in `/etc/default/vector` to pass the |
| 15 | + configuartion location, this would result in Vector failing to boot. |
| 16 | +
|
| 17 | + See the release notes for 0.15.0 for additional changes if upgrading from 0.14.X. |
| 18 | + """ |
| 19 | + |
| 20 | + commits: [ |
| 21 | + {sha: "0824874dbd0d8c6fe06cd05213c35e375caf28e3", date: "2021-08-04 14:32:23 UTC", description: "Use env vars with validate command", pr_number: 8577, scopes: ["releasing"], type: "fix", breaking_change: false, author: "Spencer Gilbert", files_count: 1, insertions_count: 19, deletions_count: 4}, |
| 22 | + |
| 23 | + ] |
| 24 | + |
| 25 | + whats_next: [ |
| 26 | + { |
| 27 | + title: "Enabling Adaptive Concurrency Control by default" |
| 28 | + description: """ |
| 29 | + We released [Adaptive Concurrency Control](\(urls.adaptive_request_concurrency_post)) in version 0.11.0 |
| 30 | + of Vector, but, up until now, this feature has been opt-in. We've been collecting user feedback, making |
| 31 | + enhancements, and expect to enable this feature as the default in 0.16.0. Users will still be able to |
| 32 | + configure static concurrency controls as they do now. |
| 33 | + """ |
| 34 | + }, |
| 35 | + { |
| 36 | + title: "End to end acknowledgements" |
| 37 | + description: """ |
| 38 | + We've heard from a number of users that they'd like improved delivery guarantees for events flowing |
| 39 | + through Vector. We are working on a feature to allow, for components that are able to support it, to |
| 40 | + only acknowledging data flowing into source components after that data has been sent by any associated |
| 41 | + sinks. For example, this would avoid acknowledging messages in Kafka until the data in those messages |
| 42 | + has been sent via all associated sinks. |
| 43 | +
|
| 44 | + This release includes support in additional source and sink components that support acknowledgements, |
| 45 | + but it has not yet been fully documented and tested. We expect to officially release this with 0.16.0. |
| 46 | + """ |
| 47 | + }, |
| 48 | + { |
| 49 | + title: "Kubernetes aggregator role" |
| 50 | + description: """ |
| 51 | + We are hard at work at expanding the ability to run Vector as an [aggregator in |
| 52 | + Kubernetes](\(urls.vector_aggregator_role)). This will allow you to build end-to-end observability |
| 53 | + pipelines in Kubernetes with Vector. Distributing processing on the edge, centralizing it with an |
| 54 | + aggregator, or both. If you are interested in beta testing, please [join our chat](\(urls.vector_chat)) |
| 55 | + and let us know. |
| 56 | +
|
| 57 | + We do expect this to be released with 0.16.0. |
| 58 | + """ |
| 59 | + }, |
| 60 | + ] |
| 61 | +} |
0 commit comments