Is this a new feature, an enhancement, or a change to existing functionality?
Enhancement
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
At present the get all VPC Peerings endpoint can be filtered by the siteId and whether the peering relationship is multi-tenant or not. However, there is no way for the user to narrow the list down to peerings that involve a particular VPC or those with a specific status.
In addition, for those VPC peering relationships that are multi-tenant, there is no indication of which tenant the other VPC belongs to.
Feature Description
As a tenant user, I want to be able to see which other tenant I am linked to when I have a multi-tenant VPC peering.
I want to be able to fetch the list of VPC peerings restricted by the following values
- one or more specific statuses
- one particular VPC involved (whether as VPC1 or VPC2)
- which particular other tenant is linked
Describe your ideal solution
Ideally we add additional filter params on the get all VPC peering endpoint
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
Enhancement
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
At present the get all VPC Peerings endpoint can be filtered by the siteId and whether the peering relationship is multi-tenant or not. However, there is no way for the user to narrow the list down to peerings that involve a particular VPC or those with a specific status.
In addition, for those VPC peering relationships that are multi-tenant, there is no indication of which tenant the other VPC belongs to.
Feature Description
As a tenant user, I want to be able to see which other tenant I am linked to when I have a multi-tenant VPC peering.
I want to be able to fetch the list of VPC peerings restricted by the following values
Describe your ideal solution
Ideally we add additional filter params on the get all VPC peering endpoint
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct