From 5f7ac0ac1d816333cae19c296cf99b469486bfea Mon Sep 17 00:00:00 2001 From: Daniel Jaglowski Date: Fri, 13 Dec 2024 17:23:13 -0500 Subject: [PATCH] [chore][connector/routing] Fix versions noted in deprecation of match_once field (#36826) --- connector/routingconnector/README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/connector/routingconnector/README.md b/connector/routingconnector/README.md index 9235cc114b67..4f88654e378a 100644 --- a/connector/routingconnector/README.md +++ b/connector/routingconnector/README.md @@ -28,16 +28,16 @@ Routes logs, metrics or traces based on resource attributes to specific pipeline ## Notice -The `match_once` field is deprecated as of `v0.115.0`. The deprecation schedule is planned as follows: +The `match_once` field is deprecated as of `v0.116.0`. The deprecation schedule is planned as follows: -- `v0.115.0`: The field is deprecated. If `false` is used, a warning will be logged. -- `v0.116.0`: The default value will change from `false` to `true`. If `false` is used, an error will be logged. -- `v0.117.0`: The field will be disconnected from behavior of the connector. If used (either `false` or `true`), an error will be logged. -- `v0.119.0`: The field will be removed. +- `v0.116.0`: The field is deprecated. If `false` is used, a warning will be logged. +- `v0.117.0`: The default value will change from `false` to `true`. If `false` is used, an error will be logged. +- `v0.118.0`: The field will be disconnected from behavior of the connector. +- `v0.120.0`: The field will be removed. ### Migration -It is recommended to set `match_once: true` until `v0.116.0` and then remove all usage of the field before `v0.119.0`. +It is recommended to set `match_once: true` until `v0.117.0` and then remove all usage of the field before `v0.120.0`. For detailed guidance on how to migrate configuration from `match_once: false` to `match_once: true`, see [Config Migration](#config-migration.md).