feat(core): add capability override layer#7520
Merged
Merged
Conversation
23 tasks
PsiACE
approved these changes
May 18, 2026
28 tasks
This was referenced May 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Refs #6707.
Rationale for this change
Some behavior test switches were encoded as service configuration even though they only control which capability-gated tests should run. This makes backend configuration mix real service behavior with test environment selection.
This PR adds a capability override layer so tests can disable selected capabilities without changing the backend's native capability declaration.
What changes are included in this PR?
CapabilityOverrideLayer, which updatesfull_capabilitywhile preservingnative_capability.OPENDAL_TEST_CAPABILITY_OVERRIDESsupport in testkit for boolean and numeric capability fields.Are there any user-facing changes?
S3 versioning, append, and write-with-if-match capabilities are now declared by default. The old S3 config toggles for these capabilities are deprecated and kept as no-op compatibility shims.
AI Usage Statement
AI assistance was used to prepare the implementation and validation steps.