Replace zfs.snapshot.* calls with pool.snapshot.* equivalents
Description
Problem/Justification
None
Impact
None
Activity
Show:
Logan Cary 16 hours agoEdited
I believe that one should also be converted in a future GE ticket, probably to pool.scan. We haven’t gotten to events much yet in the versioned API.
Ievgen Stepanovych 16 hours ago
What about zfs.pool.scan events?
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Ievgen StepanovychReporter
Logan CaryLabels
Story Points
0.5
Components
Fix versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created 21 hours ago
Updated 16 hours ago
Our 25.10 API will not include any
zfs.*endpoints (they will be private to middleware). Most zfs endpoints are already this way.The linked middleware ticket makes
zfs.snapshot.*endpoints private and creates newpool.snapshot.*endpoints as public 1:1 replacements. Replace allzfs.snapshot.*endpoints with theirpool.snapshot.*equivalents, e.g.zfs.snapshot.rollback→pool.snapshot.rollback, in the UI.The schemas remain mostly the same with the only notable difference being for
pool.snapshot.update(see middleware branch ).pool.snapshot.update.datatakes two arguments now instead of just one:user_properties_updateanduser_properties_remove. The former is an array of{"key": string, "value": string}objects, the latter is an array of string keys to remove.