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

Stuck at Lambda #32

Open
slashetcshadow opened this issue Apr 20, 2019 · 0 comments
Open

Stuck at Lambda #32

slashetcshadow opened this issue Apr 20, 2019 · 0 comments

Comments

@slashetcshadow
Copy link

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
INFO:backend:0
INFO:backend:0
aws_s3_bucket.backend_bucket: Refreshing state... (ID: slashetcshadowterraform)

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
INFO:backend:0
WARNING:lambda:terraform root: /home/user/elasticintel/terraform/dev
INFO:lambda:zipping Feed Scheduler lambda...
INFO:lambda:zipping Ingest Feed lambda...
WARNING:lambda:calling terraform from: /home/user/elasticintel/terraform/dev/lambda
Initializing modules...

  • module.lambda

Initializing the backend...

Initializing provider plugins...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

  • provider.archive: version = "~> 1.2"
  • provider.aws: version = "~> 2.7"
  • provider.template: version = "~> 2.1"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
INFO:lambda:0

  • module.lambda
    INFO:lambda:0

Error: Error asking for user input: 1 error(s) occurred:

  • provider.aws: plugin exited before we could connect

Traceback (most recent call last):
File "elasticintel.py", line 167, in
main()
File "elasticintel.py", line 113, in main
tf_helper.up_lambda(plan=args.plan)
File "/home/user/elasticintel/helpers/terraform.py", line 142, in up_lambda
LOGGER.info(subprocess.check_call(["terraform", "apply", "-var-file={}".format(self.config_file), "-auto-approve"]))
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['terraform', 'apply', '-var-file=/home/user/elasticintel/dev.conf', '-auto-approve']' returned non-zero exit status 1.
(venv) user@ubuntu:~/elasticintel$

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

No branches or pull requests

1 participant