We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
The text was updated successfully, but these errors were encountered:
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:
with
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 }}
Sorry, something went wrong.
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: