Skip to content

Conversation

@iosetek
Copy link
Contributor

@iosetek iosetek commented May 6, 2024

Awi-CLI and Awi-UI use awi-infra-guard codebase for listing most resources including VPCs. However, kube-awi uses older API from awi-grpc-catalyst-sdwan rather than awi-infra-guard.

Currently, most of methods from awi-grpc-catalyst-sdwan are forwarded to awi-infra-guard anyway, but ListVPCs is not and it was implemented to return empty list of VPCs if the connector was not VManage.

This change fixes it by using awi-infra-guard if the connector is different than VManage.

Awi-CLI and Awi-UI use awi-infra-guard codebase for listing most
resources including VPCs. However, kube-awi uses older API from
awi-grpc-catalyst-sdwan rather than awi-infra-guard.

Currently, most of methods from awi-grpc-catalyst-sdwan are
forwarded to awi-infra-guard anyway, but ListVPCs is not and it
was implemented to return empty list of VPCs if the connector was
not VManage.

This change fixes it by using awi-infra-guard if the connector is
different than VManage.
@iosetek iosetek requested a review from saswatp as a code owner May 6, 2024 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants