Giters

hashicorp / terraform

Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.

Home Page:https://www.terraform.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Terraform catchpoint resource not working

LokhandeLata opened this issue · comments

commented

Terraform Version

Terraform v1.8.5
on linux_amd64

Terraform Configuration Files

  required_providers {
    catchpoint = {
      source  = "catchpoint/catchpoint"
      version = "1.1.0"
    }
  }
  required_version = ">= 1.2.0"
}

provider "catchpoint" {
  api_token = "your_token"
}
resource "ssl_test" "chopper" {
  test_name     = "SSLTF"
  provider      = catchpoint
  division_id   = User_division_id
  product_id    = User_product_id
  folder_id     = User_folder_id
  monitor       = "ssl"
  test_location = "www.google.com"
  end_time      = "2024-10-30T04:59:00Z"
}

Debug Output

|
│ Error: 400 bad request
│ 
│   with ssl_test.chopper,
│   on main.tf line 14, in resource "ssl_test" "chopper":
│   14: resource "ssl_test" "chopper" {
│ 
╵
2024-06-22T17:56:11.720+0530 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-06-22T17:56:11.728+0530 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/catchpoint/catchpoint/1.1.0/linux_amd64/terraform-provider-catchpoint_v1.1.0 pid=223383
2024-06-22T17:56:11.728+0530 [DEBUG] provider: plugin exited

Expected Behavior

Config file is vaild, api_token is valid so terraform apply cmd should work.

Actual Behavior

Config file is vaild, api_token is valid but still it is failing at the time of terraform apply cmd.

Steps to Reproduce

  1. terraform init
  2. terraform plan
  3. terraform apply

Additional Context

terraform {
  required_providers {
    catchpoint = {
      source  = "catchpoint/catchpoint"
      version = "1.1.0"
    }
  }
  required_version = ">= 1.2.0"
}

provider "catchpoint" {
  api_token = "User_catchpoint_token"
}
resource "ssl_test" "chopper" {
  test_name     = "SSLTF"
  provider      = catchpoint
  division_id   = User_division_id
  product_id    = User_product_id
  folder_id     = User_folder_id
  monitor       = "ssl"
  test_location = "www.google.com"
  end_time      = "2024-10-30T04:59:00Z"
}

References

No response

commented

Hi @LokhandeLata, thanks for filing this! Based on the error message, I think this is likely to be an issue with the checkpoint provider rather than Terraform itself. The individual providers are managed separately, I think the checkpoint provider is managed within https://github.com/CheckPointSW/terraform-provider-checkpoint.

I'm going to close the issue here, but I'd encourage you to open an issue directly with the Checkpoint provider team.

Thanks!

commented
commented

Thanks!

commented

Above repo is for checkpoint repo, my issue is for https://github.com/catchpoint/terraform-provider-catchpoint
I cannot see any option there to create an issue, how will I get that?

commented

Ah yeah, apologies! Yeah, I totally misread the provider name!

You're right, they don't seem to allow external users to file issues via the Github repository. Unfortunately they're an entirely external company / provider so I don't have any special access either. You could try raising an issue in the Hashicorp discuss forum and tagging this provider to see if anyone else has been able to get in touch.

Alternatively, if you have an enterprise or support contract with Catchpoint directly, you might be able to get in touch with them that way.

@crw (our community manager), are you aware of any other paths of escalation we have for external / partner providers?

commented

In this case I do not think there is an internal escalation path for Catchpoint as I am not sure they are an official "partner", although I can check with the partnerships team. In any case, @LokhandeLata, if you are a customer of Catchpoint (or even if you are not) I would escalate through their support channels.