-
Notifications
You must be signed in to change notification settings - Fork 5
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
Crash while running "terraform plan" for tables a second time after creation #105
Comments
Hi @johannesploetner, thanks for the concise description, I will take a look at this |
@johannesploetner, I haven't been able to replicate this, could you please provide the .tf file that you used for this |
I basically took your code from example folder and just did some minor changes, i.e. updated the required_providers
|
Maybe this helps as well:
|
hmmm still not able to reproduce it, I have tried:
I have two suggestions for you to try, can you try:
|
I could reproduce with the newest terraform version on Mac (Intel Processor):
It still gives the error:
|
can you please run:
and send the results |
sure, here you go:
|
I'm not totally sure that this is a provider specific issue, from what I can see from other examples of this error it may be related to either your architecture or OS, are you able to confirm if you ran:
? |
It behaves same...
|
I am getting this same error on:
This happened on the first attempt to deploy the table. |
Does pinot_table need to require the table field still? It does not seem to parse any of the fields when a table config json is passed. All the table configs should be set with in the resource now? Adding tenants, segments_config, table_index_config, and metadata directly to the resource made it work. Those fields were set in the json that was passed but did not pick them up. |
I will reach out to Hashicorp about the crashing on darwin_amd64. @psheets, could you please create a separate issue about the pinot_table field, and we'll look into it there, thanks |
The provider (v.0.7.5) currently crashes if a plan is created the second time. This can be reproduced even with the example provided in the repo (I just modified the table from a REALTIME table to a OFFLINE table because I didn't had a Kafka at hand)
steps to reproduce:
expected behavior: "terraform plan" works & no changes to the plan
actual behavior:
The text was updated successfully, but these errors were encountered: