Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid character '<' looking for beginning of value #1559

Closed
wojukasz opened this issue Sep 8, 2022 · 1 comment · Fixed by #1560
Closed

invalid character '<' looking for beginning of value #1559

wojukasz opened this issue Sep 8, 2022 · 1 comment · Fixed by #1560

Comments

@wojukasz
Copy link

wojukasz commented Sep 8, 2022

Terraform Version

Terraform v1.2.8

Affected Resource(s)

  • data: datadog_ip_ranges

Terraform Configuration Files

provider "datadog" {
  api_url = "https://api.datadoghq.eu/"
  api_key = var.api_key
  app_key = var.app_key
}

terraform {
  required_providers {
    datadog = {
      source  = "datadog/datadog"
      version = "= 3.15"
    }
  }
}

data "datadog_ip_ranges" "this" {}

output "datadog_ip_ranges" {
  value = data.datadog_ip_ranges.this
}

Debug Output

data.datadog_ip_ranges.this: Reading...
╷
│ Error: invalid character '<' looking for beginning of value
│
│   with data.datadog_ip_ranges.this,
│   on datadog.tf line 16, in data "datadog_ip_ranges" "this":
│   16: data "datadog_ip_ranges" "this" {}
│

Expected Behavior

terraform plan to succed and provide IP ranges.

Actual Behavior

terraform plan failed to provide IP ranges with following error:
Error: invalid character '<' looking for beginning of value

Steps to Reproduce

Use above terraform hcl code snippet,

  1. populate variables: app_key, api_key
  2. terraform init
  3. terraform plan

Important Factoids

This issue doesn't occur with datadog provider 3.14.
Changing version = "= 3.15" to 3.14 results with working plan.

References

Other issue with same error:
#1065
#364
#364

@skarimo
Copy link
Member

skarimo commented Sep 8, 2022

We just released v3.15.1 with the fix included. Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants