Repository navigation
CLDSRV-1057: move the D1 epic to Arsenal 8.7.0 - #6350
Open
anurag4DSB wants to merge 3 commits into
Open
anurag4DSB wants to merge 3 commits into
anurag4DSB wants to merge 3 commits into
Conversation
ubuntu-latest moved to 26.04, which has no Python 3.9 for setup-python. Issue: CLDSRV-1052 (cherry picked from commit fef349d)
Arsenal 8.7.0 carries the bucketnotif IAM actions and the arn:scality:bucketnotif resource that the notification destination request contexts need. The lock holds one Arsenal entry, shared with the ^8.6.0-0 range of utapi and the bucketclient peer, so node_modules has a single copy and the errors identity checks keep working. The rest of the lock change is the OpenTelemetry versions that Arsenal 8.7.0 requires.
…m an unconfigured KMS Pass the requested key ARN to Arsenal at both checks. The functional-test hunk was left out because this branch has no multi-KMS suite. (cherry picked from commit 4be78a8)
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
dvasilas
approved these changes
Nov 4, 2026
This branch has not been deployed
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.
Intent: why does this change exist?
The D1 epic moves to Arsenal 8.7.0, so that CloudServer, backbeat and Vault run the same Arsenal. This PR holds the bump and the two upstream fixes it needs, apart from the bucketnotif work that sits on it.
System impact: what's affected, including downstream?
Arsenal moves to 8.7.0, one copy shared with utapi, which also moves OpenTelemetry from 0.220 to 0.223 and from 2.9 to 2.12. Arsenal 8.7.0 adds a third
validateKeyDetailargument, so the upstream fix for that call is cherry-picked from development/9.6, without its multi-KMS functional-test hunk. The KMS CI jobs are pinned to ubuntu-24.04, also picked from upstream, because ubuntu-latest moved to 26.04, where setup-python has no Python 3.9.Preserved behavior: what explicitly stays the same?
CloudServer behaves the same apart from one KMS error text: the D1 additions of Arsenal 8.7.0 stay off unless a caller opts in.
Intended change: what's different after this PR?
A rejected key of an unconfigured KMS provider names the requested key ARN instead of
undefined.Verification: how do we know this worked, or how would we know if it didn't?
The unit suite and lint pass on Node 24.16.0, and the KMS suites pass with the ubuntu-24.04 pin. Both picks keep the patches of their upstream commits, so a later rebase onto development drops them.