UI: Fixes and minor enhacements to the Public IP Addresses section #10351
+15
−5
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
In the Public IP Addresses UI section, the options to release reserved IPs (
releaseIpAddress
API) and disassociate IPs (disassociateIpAddress
API) are always available through group actions, regardless of the public IP's state. Additionally, the option to disassociate IPs is available for IPs in use by system VMs, both through group actions anddataView
.This PR fixes these UI bugs. Furthermore, a label, similar to the existing ones for
source-nat
andstatic-nat
, was created to indicate that a public IP is in use by a system VM. Lastly, theallocated
column in theListView
, that represents the datetime an IP was allocated, is now parsed and formatted according to the user's timezone.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
disassociateIpAddress
through group actions:releaseIpAddress
through group actions:How Has This Been Tested?
vpc-01
) and acquired two additional public IPs;system
tag;allocated
datetime was correctly parsed and formatted according to the timezone in use;system
IPs were not available through group actions ordataView
;source-nat
IPs were not available through group actions ordataView
;Reserved
IPs.