You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good to have the VCN name associated to ListSubnets, ListSecurityLists, ListNetworkSecurityGroups api's apart from the vcn_id field to avoid unnecessary joins to get the VCN name associated to the respective security list, subnet or group.
The text was updated successfully, but these errors were encountered:
bigdatasourav
changed the title
add support for vcn name in response for ListSubnets ,ListSecurityLists,ListNetworkSecurityGroups api's apart from vcn id.
add support for vcn name in response for ListSubnets , ListSecurityLists, ListNetworkSecurityGroups api along with vcn_id.
Jun 16, 2021
bigdatasourav
changed the title
add support for vcn name in response for ListSubnets , ListSecurityLists, ListNetworkSecurityGroups api along with vcn_id.
add support for vcn name in response for ListSubnets, ListSecurityLists, ListNetworkSecurityGroups api along with vcn_id.
Jun 16, 2021
bigdatasourav
changed the title
add support for vcn name in response for ListSubnets, ListSecurityLists, ListNetworkSecurityGroups api along with vcn_id.
add support to include VCN name in List API response.
Jun 16, 2021
It would be good to have the VCN name associated to ListSubnets, ListSecurityLists, ListNetworkSecurityGroups api's apart from the vcn_id field to avoid unnecessary joins to get the VCN name associated to the respective security list, subnet or group.
The text was updated successfully, but these errors were encountered: