Skip to content

Remove the pensieve management backend - #2865

Draft
francoisferrand wants to merge 1 commit into
development/9.6from
improvement/BB-896-remove-pensieve-backend
Draft

francoisferrand wants to merge 1 commit into
development/9.6from
improvement/BB-896-remove-pensieve-backend

Conversation

@francoisferrand

Copy link
Copy Markdown
Contributor

The pensieve backend implemented the Zenko 1.x Orbit flow: read the configuration overlay from the PENSIEVE metadata bucket, decrypt the secrets and patch the location constraints into the running config. Nobody deploys Backbeat that way anymore — zenko-operator always sets MANAGEMENT_BACKEND=operator, so the operator backend is the only one in use. MANAGEMENT_BACKEND is now simply ignored.

Beyond being dead code, patchConfiguration.js pulled in arsenal.patches.locationConstraints.patchLocations at load time in every Backbeat process, which kept Arsenal from dropping its pensieve helpers (ARSN-653). patchConfiguration.js now only keeps the ingestion bucket refresh used by the operator backend.

Also drops the now-unused convertServiceStateFormat, the PENSIEVE test fixtures and the MANAGEMENT_BACKEND mentions in docs/CI.

Related: CLDSRV-1013 (same cleanup in CloudServer).

Issue: BB-896

The pensieve backend implemented the Zenko 1.x Orbit flow: read the
configuration overlay from the PENSIEVE metadata bucket, decrypt the
secrets and patch the location constraints into the running config.
Nobody deploys Backbeat that way anymore: zenko-operator always sets
MANAGEMENT_BACKEND=operator, so the operator backend is the only one
actually in use. MANAGEMENT_BACKEND is now simply ignored.

Beyond being dead code, patchConfiguration.js pulled in
arsenal.patches.locationConstraints.patchLocations at load time from
every Backbeat process, which kept Arsenal from dropping its pensieve
helpers (ARSN-653). patchConfiguration.js now only keeps the ingestion
bucket refresh used by the operator backend.

Issue: BB-896
@bert-e

bert-e commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Hello francoisferrand,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval ⭐
/bypass_build_status Bypass the build and test status ⭐
/bypass_commit_size Bypass the check on the size of the changeset TBA ⭐
/bypass_incompatible_branch Bypass the check on the source branch prefix ⭐
/bypass_jira_check Bypass the Jira issue check ⭐
/bypass_peer_approval Bypass the pull request peers' approval ⭐
/bypass_leader_approval Bypass the pull request leaders' approval ⭐
/bypass_source_branch_lineage Bypass the cross-branch contamination check ⭐
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request.
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e

bert-e commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

Comment thread docs/run-oob-locally.md

```
MANAGEMENT_BACKEND=operator REMOTE_MANAGEMENT_DISABLE=true yarn start
REMOTE_MANAGEMENT_DISABLE=true yarn start

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only the deleted pensieveBackend.js read REMOTE_MANAGEMENT_DISABLE, so it does nothing in Backbeat now (you also took it out of docs/configuration.md). Drop it here too. Other places still set it for Backbeat: README.md, docs/run-transition-locally.md, docs/run-crr-replay-locally.md and .github/dockerfiles/ft/docker-compose.yaml.

Suggested change
REMOTE_MANAGEMENT_DISABLE=true yarn start
yarn start

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants