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

   ### Description
   
   Currently, the description of backup events contains the backup's internal 
ID, displaying sensitive content to users. This PR changes the events 
description to use the backup's UUID instead.
   
   ### 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)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [X] 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> Before the changes: </summary>
   
   <img width="2964" height="287" alt="image" 
src="https://github.com/user-attachments/assets/adb30a0c-5083-41e8-9ef9-b132d21b0d4e";
 />
   
   </details>
   
   <details> <summary> After the changes: </summary>
   
   <img width="3082" height="747" alt="image" 
src="https://github.com/user-attachments/assets/519cd39d-e130-45ee-bcc9-274d20a6cb5b";
 />
   
   </details>
   
   
   ### How Has This Been Tested?
   
   After changing the code, I compiled the code and installed the packages to 
my lab. Then, I created a VM to perform the tests and assigned it a backup 
offering. After that, I created a test backup, restored it, and deleted it. 
When the `Events` tab was accessed, I validated that the events displayed the 
backup's UUID, instead of its internal ID.
   
   #### How did you try to break this feature and the system with this change?


-- 
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