-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat(config): graduated deprecation policy for removed config fields #25356
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
Open
joshcoughlan
wants to merge
1
commit into
vectordotdev:master
Choose a base branch
from
Automattic:chore/api-deprecate-playground-graphql
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| Configurations carrying the removed `api.playground` or `api.graphql` fields no longer fail to load. Both options were dropped in 0.55.0 along with the GraphQL observability API; setting them now is accepted at deserialize time but logs a deprecation warning at startup, and the values are otherwise ignored. This makes upgrades from 0.54.0 and earlier non-breaking when those fields are still present in pinned configs. | ||
|
|
||
| The deprecation follows a graduated policy: the field is accepted with a `warn!` at startup for `WARN_WINDOW_MINORS = 12` minor releases after the version in which it was removed (about a year at Vector's monthly cadence), and the warning text names the exact future version in which the field becomes a hard configuration error. Once that future version ships, an attempt to load a config that still sets the field fails fast with a clear "remove this field" message — no silent breaking changes. Operators have a deterministic deadline for cleanup. | ||
|
|
||
| The policy lives in a new reusable module, `src/config/deprecation`, so future field removals can opt into the same behavior with a single call site rather than reimplementing per-field warnings. | ||
|
|
||
| Remove `api.playground` / `api.graphql` from your configuration to silence the warning — they have no runtime effect. | ||
|
|
||
| authors: joshcoughlan |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 change enforces
api.check_deprecated_fields()only inApplicationConfig::from_config, so the new hard-error stage is bypassed anywhere aConfigis loaded without going through that constructor (notablyvector validateand runtime reloads via--watch-config/SIGHUP). In those paths, configs that should be rejected after the warn window can still be accepted, which breaks the promised “deterministic deadline” and causes inconsistent behavior between validation/reload and cold start.Useful? React with 👍 / 👎.