Allow IPs for Terraform Cloud about terraform-provider-namecheap HOT 10 CLOSED

After some experimentation, I found that 2 IPs that have failed so far are part of AWS us-east-2, and another is in us-east-1. I understand that it is probably undesirable to allow entire AWS CIDR ranges so #59 may not solve this after all.

from terraform-provider-namecheap.

I don't know the Namecheap internals but their systems might take a few minutes to fully update each allowed IP.

from terraform-provider-namecheap.

Hi!
Unfortunately this is a limitation of the Namecheap public API itself, rather than Terraform provider. Also there is no way to change whitelist via API as far as I know :(

I would advice you to contact our customer support team. They do track such client requests and as soon as there is enough demand on certain feature - it get's processed by respective product team.

from terraform-provider-namecheap.

This seems to make the Namecheap provider totally unusable when Terraform Cloud is the backend. I keep whitelisting new IPs, but from the TFC side it seems that the IPs are dynamic, so it fails every time.

It's pretty hard to do anything real with this provider if the underlying API breaks on requiring whitelisting something that Terraform Cloud doesn't have (static IPs).

This is quite a bummer as I was really looking forward to using this provider.

from terraform-provider-namecheap.

As @tedmiston said, I wanted to use this provider but am blocked by the requirement to whitelist IP addresses.

• What do you do if you want to run the Terraform locally?
• What do you do if you are using Terraform Cloud?

from terraform-provider-namecheap.

That's really confusing to have build a Terraform module but having this limitation. Allowing a range of IP addresses should be a good way to workaround this.

Maybe having some kind of "Profiles" for well known CI/CD platforms, holding there runners IP CIDR, would even be better.

from terraform-provider-namecheap.

Even without a Namecheap API that updates the whitelist, maybe a provider for updating the whitelist could be made to drive the webpage that takes the input.

In that way, the namecheap provider could depend on the namecheap whitelist provider. When running in Terraform Cloud, a "data" provider could then determine the source IP on the fly and open the door ahead of actual API calls.

Just an idea. This is a major bummer when I just booked a domain with Namecheap for several years. :(

from terraform-provider-namecheap.

I've added Namecheap provider to our infrastructure but had to completely remove it since we are unable to run this in a CI/CD, which makes this provider basically useless if you don't have a static IP.

from terraform-provider-namecheap.

For people who might still be struggling with this issue, here are some resources that can help you:

• https://developer.hashicorp.com/terraform/cloud-docs/agents
• https://developer.hashicorp.com/terraform/tutorials/cloud/cloud-agents

#59 #67

from terraform-provider-namecheap.

Duplicate of #59

from terraform-provider-namecheap.