It is inevitable that Vector will rename and reorganize configuration options, #3714 is the latest example. And while these changes are simple, they break backward compatibility and negatively affect UX. In the past we've simply aliased names so that we maintain backward compatibility, but we don't do this in a way that informs the user or marks the option as explicitly deprecated. This means it's unlikely we'll ever clean up this option.
I propose that we formalize how we deprecate options. It would be nice to create a single place where we define deprecated options. This place would perform the mapping as well as long deprecation warnings for users using these options.
It is inevitable that Vector will rename and reorganize configuration options, #3714 is the latest example. And while these changes are simple, they break backward compatibility and negatively affect UX. In the past we've simply aliased names so that we maintain backward compatibility, but we don't do this in a way that informs the user or marks the option as explicitly deprecated. This means it's unlikely we'll ever clean up this option.
I propose that we formalize how we deprecate options. It would be nice to create a single place where we define deprecated options. This place would perform the mapping as well as long deprecation warnings for users using these options.