Bump pensieve-api & release 2.14.1#2358
Merged
bert-e merged 28 commits intodevelopment/2.14from Mar 19, 2026
Merged
Conversation
Remove Ceph RADOSGW capability flags from zenkoversion defaults so Ceph is no longer advertised as a supported backend.
Delete Ceph-in-a-box scripts and chart resources from GitHub automation now that Ceph targets are no longer used in Zenko CI.
Issue: ZENKO-5202
Replace the three scalar World keys (identityNameForScenario,
identityTypeForScenario, accountNameForScenario) with a typed
SavedIdentity[] array. This makes multiple identities naturally
queryable and eliminates manual additionalAccountNames tracking.
- Add SavedIdentity interface and getSavedIdentities/getSavedIdentity helpers
- saveIdentityInformation now appends to the array
- useSavedIdentity uses getSavedIdentity() (defaults to last entry)
- Migrate direct getSaved reads in bucket-policies and iam-policies
- Simplify "{int} additional accounts" step
- Drop additional accounts After cleanup hook
Issue: ZENKO-5202
Use the existing data_consumer Keycloak user (which has the DataConsumer role, not StorageManager) instead of introducing a dedicated norights user. This removes the KeycloakUsernameNoRights world parameter and reuses the existing DataConsumerUsername parameter. Issue: ZENKO-5202
Call prepareMetricsScenarios directly in the Before hook instead of going through an unnecessary indirection layer. Issue: ZENKO-5202
Add optional size parameter to putObject and uploadSetup so callers can pass the object size directly rather than routing it through the World saved-state dictionary. Issue: ZENKO-5202
… groups Collapse permission scenarios into a single parameterized Scenario Outline with role/expectedStatus examples. Separate content tests (structure, multi-account, metrics) into their own group. Replace two hardcoded When steps with a single parameterized step using a role-to-username lookup. Issue: ZENKO-5202
Disable camelcase rule for role-to-username map keys (must match Keycloak usernames). Shorten step names and parameter names to stay within 120-char line limit. Issue: ZENKO-5202
The roleToWorldParam lookup resolved role names to ctst_-prefixed usernames (e.g. ctst_storage_manager) which are not valid for direct Keycloak token acquisition. Pass the role string directly instead, matching how managementAPIRequest works elsewhere. Issue: ZENKO-5202
The SavedIdentity refactor changed useSavedIdentity to read from an array, but getSavedIdentity returns undefined when no identity was saved. This crashed CountItems which calls useSavedIdentity via 'the operation finished without error' without prior identity setup. Match old behavior by returning early when no identity exists. Issue: ZENKO-5202
- Rename "role" to "persona" in feature file and step definitions
- Replace hardcoded Keycloak usernames with World parameter keys
- Add Given step for persona setup, decoupled from When action
- Split into "tries to retrieve" (no status check) and "retrieves" (asserts 200)
- Add generic "Then the http response code is {int}" step in common
- Remove section comments from feature file
Issue: ZENKO-5202
World parameter keys (StorageManagerUsername, DataConsumerUsername) resolve to ctst_-prefixed usernames which lack the instanceIds Keycloak attribute required by the management API. Use the base Keycloak usernames directly. Issue: ZENKO-5202
Remove Ceph references from supported cloud lists and location management guidance, and generalize bucket-match wording to S3-compatible endpoints.
The ctst Dockerfile hardcoded ghcr.io/scality as the registry for sorbet and drctl images, ignoring the sourceRegistry field in deps.yaml. This meant changing sourceRegistry (e.g. to a playground fork) had no effect on CI test builds. Extract the full image path (sourceRegistry + image) from deps.yaml using yq in the workflow, and pass it as Docker build args. The Dockerfile now uses SORBET_IMAGE and DRCTL_IMAGE ARGs with backward-compatible defaults. Issue: ZENKO-5220
Bump @aws-sdk/client-s3 to ^3.931.0 SDK versions 3.929.0-3.930.0 have a regression (aws/aws-sdk-js-v3#7500) in REST protocol deserialization that causes empty XML responses to fail with "Expected object, got string". This affects GetObjectAttributes when no matching attributes are found (e.g. requesting non-existent user metadata keys). Fixed in 3.931.0 by aws/aws-sdk-js-v3#7501. Issue: ZENKO-5208
…t-attributes' into improvement/ZENKO-5210
…-support' into improvement/ZENKO-5210
…sourceregistry' into improvement/ZENKO-5210
…orting-route' into improvement/ZENKO-5210
Contributor
Hello francoisferrand,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Contributor
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
delthas
approved these changes
Mar 18, 2026
Contributor
Author
|
/bypass_peer_approval |
Contributor
Author
|
/approve |
Contributor
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue ZENKO-5210. Goodbye francoisferrand. The following options are set: bypass_peer_approval, approve |
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
5 participants
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.
Issue: ZENKO-5210