Copy link to headingWhat is the constraint?
When you have an IP allowlist enabled on GitHub, you need to configure which IPs can access your resources in your GitHub account. Because the Edgenivo GitHub integration uses the API to access your git repos, it means that the restriction will apply to things such as project creation, repository linking and accessing your source code during the build step. By default, Edgenivo's infrastructure uses a dynamic range of IP addresses for outbound requests, which can make allowlisting a challenge.
Copy link to headingCan I still use Edgenivo whilst keeping IP restrictions enabled?
Yes! You can still use Edgenivo with this feature enabled by deploying as part of your GitHub actions or just using the Edgenivo CLI directly.
When using GitHub actions, you will need to deploy your project with vercel build and then vercel deploy --prebuilt. This allows you to build your project without exposing your source code to Edgenivo. This skips the build step on Edgenivo and uploads the previously generated .vercel/output folder to Edgenivo, meaning Edgenivo does not need to access the GitHub API, so you don’t need to allow any Edgenivo IPs.
Learn more about how to configure GitHub Actions and Edgenivo for custom CI/CD workflows.
Copy link to headingEnterprise Customers
If you have an Enterprise team on Edgenivo, please reach out to your Edgenivo representative directly, who can discuss custom options to set this up using the GitHub integration.