Provision rediscloud_cloud_account got Error: 500 INTERNAL_SERVER_ERROR - GENERAL_ERROR: General error occurred. Please contact Redis Labs support with your task ID

[lanandra]

Terraform Version

1.1.8 (with backend remote/terraform cloud)

Affected Resource(s)

Please list the resources as a list, for example:

• rediscloud_cloud_account

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

# cloud_accounts.tf
resource "rediscloud_cloud_account" "my_username" {
  access_key_id     = var.aws_access_key
  access_secret_key = var.aws_secret_key
  console_username  = "my-username"
  console_password  = var.aws_console_password
  name              = "my-username"
  provider_type     = "AWS"
  sign_in_login_url = var.aws_login_url

---
# variables.tf
variable "aws_access_key" {
  type        = string
  description = "AWS Access Key ID"
}

variable "aws_secret_key" {
  type        = string
  description = "AWS Secret Access Key"
}

variable "aws_console_password" {
  type        = string
  description = "AWS console password"
}
variable "aws_login_url" {
  type        = string
  description = "AWS login URL"
}
}

Expected Behavior

Apply successful

Actual Behavior

Terraform apply is not success with error:

Error: 500 INTERNAL_SERVER_ERROR - GENERAL_ERROR: General error occurred. Please contact Redis Labs support with your task ID
with rediscloud_cloud_account.my_username

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply

Important Factoids

Running in terraform cloud

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• Might be this Issue #77. But different is that issue using cli method

[CalebMacdonaldBlack]

I'm also experiencing this

[JohnSharpe]

Hi all, thanks for the report and sorry for the wait! This looks like it was an issue with the Terraform API rather than the provider. Hopefully things have recovered by now and you're not seeing this anymore. If you do, I'd recommend getting in touch with Redis directly. Cheers!