airbnb / binaryalert

BinaryAlert: Serverless, Real-time & Retroactive Malware Detection.
https://binaryalert.io
Apache License 2.0
1.4k stars 187 forks source link

Error loading configuration issue #111

Closed boodera closed 6 years ago

boodera commented 6 years ago

Background

I followed the steps for deployment of binaryalert using ubuntu based EC2 instance, with all configurations done. When I ran './manage.py deploy' , it displayed this error

Error loading configuration: Error loading /home/ubuntu/binaryalert/terraform/cloudwatch_dashboard.tf: Error reading config for aws_cloudwatch_dashboard[binaryalert]: local.dashboard_body: resource variables must be three parts: TYPE.NAME.ATTR in: ${local.dashboard_body} Traceback (most recent call last): File "./manage.py", line 488, in main() File "./manage.py", line 484, in main manager.run(args.command) File "./manage.py", line 348, in run getattr(self, command)() # Command validation already happened in the ArgumentParser. File "./manage.py", line 421, in deploy self.apply() File "./manage.py", line 372, in apply subprocess.check_call(['terraform', 'init']) File "/usr/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['terraform', 'init']' returned non-zero exit status 1.

Can you please suggest any configuration mistake I may have done, or is it a known bug?

austinbyers commented 6 years ago

Hi @boodera! I don't think we've seen this before. My guess is that you're running an older version of Terraform. What is the output of terraform --version? Try upgrading Terraform to the latest version (0.11.X).

You can test whether Terraform understands the config by cd terraform && terraform validate

austinbyers commented 6 years ago

I'm closing the issue for now, but feel free to re-open if you're still experiencing any issues!