User Experience: Allow users to add Description to Private Gateway an… #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces the ability to add descriptions to Private Gateways and Static Routes within the CloudStack UI. The enhancement aims to improve the maintainability and clarity of network configurations as users scale up the number of gateways and routes. Currently, the UI lacks a way to note what each gateway or route is intended for, leading to confusion especially in environments with multiple administrators. By allowing users to annotate their configurations, this update will make it easier to understand and manage network setups.
Fixes: # 8837
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
This feature was tested on CloudStack 4.19, using multiple configurations of Private Gateways and Static Routes. I created several scenarios with varying numbers of gateways and routes to ensure the description fields are visible and functional across different setups. Additional tests were performed to verify that the descriptions persist after edits and are visible to all users with appropriate permissions.
How did you try to break this feature and the system with this change?
Tests included attempting to input excessively long descriptions, special characters, and HTML tags to ensure input validation is properly handled. I also tested the feature's interaction with existing functionalities such as the creation and deletion of gateways and routes to ensure there are no regressions.
Please read the CONTRIBUTING document for more details on contributing to CloudStack.