Skip to content

merge queue: embarking main (b5a7205) and #79 together#80

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/ea9f55edf0
Closed

merge queue: embarking main (b5a7205) and #79 together#80
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/ea9f55edf0

Conversation

@mergify
Copy link
Copy Markdown

@mergify mergify Bot commented May 15, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (b5a7205) and #79 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #79.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: b5a7205f6a795857b6c100abd4c9438902addd49
previous_failed_batches: []
pull_requests:
  - number: 79
    scopes: []
scopes: []
...

nicknevin and others added 2 commits May 12, 2026 08:50
Introduce a new RPC `GetReplicationDestinationInfo` with a corresponding
capability `GET_REPLICATION_DESTINATION_INFO`. This RPC can be called to
retrieve the current destination volume or volume group details, including
per-volume ID mappings for dynamic groups.

This is necessary to support storage providers which have different volume IDs
and volume group IDs on the source and destination sides of a replication
relationship.

Signed-off-by: Nick Nevin <nnevin@redhat.com>
@mergify mergify Bot closed this May 15, 2026
@mergify mergify Bot deleted the mergify/merge-queue/ea9f55edf0 branch May 15, 2026 05:53
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.

1 participant