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

Terraform crash when working with NS1 feeds/sources #21065

Closed
dangoldin opened this issue Apr 22, 2019 · 2 comments
Closed

Terraform crash when working with NS1 feeds/sources #21065

dangoldin opened this issue Apr 22, 2019 · 2 comments

Comments

@dangoldin
Copy link

Terraform Version

Terraform v0.11.13
+ provider.ns1 v1.3.0

Terraform Configuration Files

This is happening during the plan phase when I manually added a feed to a record and am trying to get Terraform to show the plan of removing it.

Debug Output

2019-04-21T23:31:38.432-0400 [DEBUG] plugin.terraform-provider-ns1_v1.3.0_x4: 2019/04/21 23:31:38 got meta:  &{<nil> map[feed:5cb8f7e5a632f60001771641] <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil>}
... and a few lines down ...
panic: expected v to be convertible to a string, got: map[feed:XXXXXXX], map[string]interface {}

Crash Output

I'm hesitant to post due to sensitive contents but can try to come up with a toy example if it's helpful. Generally seems the issue is due to NS1 feeds/sources being setup to support a different type (string vs map).

Expected Behavior

Terraform would be able to ingest the feed info from NS1.

Actual Behavior

Terraform crashed.

Steps to Reproduce

  1. Create a simple NS1 record using Terraform.
  2. Go into NS1 and add a filter chain to use that record.
  3. Run terraform plan.

Additional Context

Nope - pretty standard terraform.

References

NA

@ghost
Copy link

ghost commented Apr 22, 2019

This issue has been automatically migrated to terraform-providers/terraform-provider-ns1#53 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to terraform-providers/terraform-provider-ns1#53.

@ghost ghost closed this as completed Apr 22, 2019
@ghost
Copy link

ghost commented Jul 26, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Jul 26, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants