Support for multiple virtual networks

[martinhausio]

Hi, we have multiple virtual networks in our setup and would like to be able to choose which one the action will connect to.

the warp-cli supports this by configuring the vnet parameter, passing it the vnet ID prior to connecting

example:

warp-cli vnet abcd1234-12ab-34bc-1234-a12344321a

warp-cli connect

[F21]

Would you be happy to open a PR to implement this?

I think we can add it as a with parameter in the action's configuration:

uses: Boostport/setup-cloudflare-warp@v1
with:
  organization: your-organization
  auth_client_id: ${{ secrets.CLOUDFLARE_AUTH_CLIENT_ID }}
  auth_client_secret: ${{ secrets.CLOUDFLARE_AUTH_CLIENT_SECRET }}
  vnet: ${{ secrets.CLOUDFLARE_VNET }}

[giriparus]

I can pick this up soon, over this or the next weekend. I was also thinking of adding another parameter "profile" in case you have different profiles to differentiate between the split tunnels they use as well.

[bruce-szalwinski-he]

we put a wrapper around setup-cloudflare-warp that takes an additional parameter for the virtual network. We call the base action and then shell out to command line to switch to the selected virtual network, if supplied. It works mostly, but we have to do some shenanigans to force the route table to include the CloudflareWarp entries.

That is, after we run setup-cloudflare-warp and switch to selected vnet, ip route show table all does not include the CloudFlare warp entries. We sit in a loop and try to connect to an RDS inside the VPC (the shenanigans). It eventually succeeds. Then running ip route show table all now shows CloudflareWarp entries.