Whitelist IPs for known CICD providers about terraform-provider-namecheap HOT 5 CLOSED

I'd be curious about this too, what is the point of having an API if it can't be used in a production setting? Is it only meant for hobbyists toying with the API from their laptops? Or is it the other extreme, meant for large enterprises (but not too large, as the max of 20 can't be increased) who can operate their own servers with dedicated IPs?

from terraform-provider-namecheap.

Even for CI providers with more fixed set if IP adresses this is pretty difficult. Github provides a list of all their used IP ranges, and for github actions, it looks like they use a pool of a few thousands to ten thousands IP addresses (https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses). This is kind of difficult to use with Namecheaps maximum of 20 whitelisted IP adresses. So this pretty much means this is not usable with the majority of CICD providers at the moment.

from terraform-provider-namecheap.

Hey,
we support whitelist during API key creation in your account.

As for global whitelist - we don't have that in plan, and unfortunately in nearest future we do not consider doing that.

from terraform-provider-namecheap.

The problem is that IPs for e.g., Terraform Cloud, are dynamic. I do not think there is actually a whitelist one can use. I just get failed apply after failed apply because of this issue with the Namecheap provider / API (see #62).

from terraform-provider-namecheap.

Duplicate of #59

from terraform-provider-namecheap.