erikbocks opened a new pull request, #14255:
URL: https://github.com/apache/cloudstack/pull/14255

   ### Description
   
   Currently, the backup's path in the secondary storage is not displayed in 
the GUI, being necessary to query it directly from the database. Therefore, the 
`backuppaths` attribute, with the path of the backup of each VM's disk was 
added to the `listBackups` API response, and to the backup details in the GUI. 
Only Root Admin accounts are allowed to view the backup paths in the GUI and in 
the API response. Currently only supported by `KBOSS` provider.
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [X] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [X] Minor
   
   ### Screenshots (if appropriate):
   
   <details><summary>Backup paths in the GUI</summary>
   
   <img width="2202" height="1145" alt="Screenshot from 2026-09-28 14-43-08" 
src="https://github.com/user-attachments/assets/eb056372-c36c-4503-ad6c-25de0ac0ec88";
 />
   
   </details>
   
   ### How Has This Been Tested?
   
   I configured KBOSS as the backup provider, and created a new backup of an 
existing VM. Then, I accessed the backup's details tab and validated that the 
new field was added successfully. I also validated that the `backuppaths` 
attribute was present at the `listBackups` API response.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to