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

   ### Description
   
   The classes AgentProperties and AgentPropertiesFileHandler were previously 
created to map the existing properties of the agent.properties file to 
facilitate their use; however, only a few properties were mapped at the time.
   
   This PR aims to build on those changes. All of the properties of the 
agent.properties file were mapped in the AgentProperties class.
   While executing the mapping, I found some properties that were used in the 
code, but were not documented in the "agent.properties" file. These properties 
were also documented, and registered accordingly in the properties file.
   
   The way the properties were accessed in the code was changed, and now the 
values are obtained through the AgentPropertiesFileHandler class. Also, Unit 
Tests were added and modified according to necessity. 
   
   ### 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)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [x] Major
   - [ ] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   
   ### Screenshots (if appropriate):
   
   
   ### How Has This Been Tested?
   This was manually tested in a local lab, by altering properties and 
performing main actions: creating and deleting VMs, creating new Volumes and 
snapshots, etc.
   


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