Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Error on the "uptimerobot_alert_contact" data #29

Closed
nlamirault opened this issue May 24, 2019 · 6 comments
Closed

Error on the "uptimerobot_alert_contact" data #29

nlamirault opened this issue May 24, 2019 · 6 comments

Comments

@nlamirault
Copy link
Contributor

nlamirault commented May 24, 2019

Hi,
i would try the new data/resources "alert_contact", but i've got some errors :

$ terraform init

Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...

Provider "uptimerobot" not available for installation.

A provider named "uptimerobot" could not be found in the official repository.

This may result from mistyping the provider name, or the given provider may
be a third-party provider that cannot be installed automatically.

In the latter case, the plugin must be installed manually by locating and
downloading a suitable distribution package and placing the plugin's executable
file in the following directory:
    terraform.d/plugins/linux_amd64

Terraform detects necessary plugins by inspecting the configuration and state.
To view the provider versions requested by each module, run
"terraform providers".

Install the provider :

$ cp terraform-provider-uptimerobot ~/.terraform.d/plugins/linux_amd64/

Terraform actions :

$ terraform init

Initializing provider plugins...

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

$ terraform plan -var-file=../personal/galactus.tfvars 

Error: data.uptimerobot_alert_contact.default_alert_contact: Provider doesn't support data source: uptimerobot_alert_contact

With this code :

data "uptimerobot_account" "account" {}

data "uptimerobot_alert_contact" "default_alert_contact" {
  friendly_name = "${data.uptimerobot_account.account.email}"
}

resource "uptimerobot_monitor" "google_com" {
  url           = "http://google.com"
  type          = "http"
  friendly_name = "Google"
}

Any idea ?

@nlamirault nlamirault changed the title Error on the Error on the "uptimerobot_alert_contact" data May 24, 2019
@drubin
Copy link
Contributor

drubin commented May 24, 2019

Hi @nlamirault #21 this was only merged 18 hours ago and hasn't been published as a release yet.

You can check out the master branch and compile it your self and then your instructions should work.

Hope this helps and that @louy will publish a release soon.

@nlamirault
Copy link
Contributor Author

Hi @drubin i sw that. But i've build the master branch before my test.

$ go build .
$ mv ./terraform-provider-uptimerobot ~/.terraform.d/plugins/linux_amd64/
$ lt ~/.terraform.d/plugins/linux_amd64/terraform-provider-uptimerobot 
.rwxr-xr-x  nicolas  users  26.2 MB  Fri May 24 17:32:43 2019    terraform-provider-uptimerobot
$ terraform init

Initializing provider plugins...

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
$ terraform plan -var-file=../personal/galactus.tfvars 

Error: data.uptimerobot_alert_contact.default_alert_contact: Provider doesn't support data source: uptimerobot_alert_contact

@caarlos0
Copy link
Contributor

caarlos0 commented Jun 3, 2019

I just built from master here and it works...

@louy
Copy link
Owner

louy commented Oct 4, 2019

Hi guys. I know it's been a while. Is this still an issue or can we close it?

@caarlos0
Copy link
Contributor

caarlos0 commented Oct 4, 2019

@louy I'm using a build from master and it was working fine...

@louy
Copy link
Owner

louy commented Oct 4, 2019

I'll close this issue then. Feel free to file a new one if you face this problem again!

@louy louy closed this as completed Oct 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants