You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apart form the upgrade to .12 being needed, it looks like a few variables names are being used that aren't allowed now, like 'provider'.
Warning: Skipping backend initialization pending configuration upgrade
The root module configuration contains errors that may be fixed by running the
configuration upgrade tool, so Terraform is skipping backend initialization.
See below for more information.
Warning: Quoted type constraints are deprecated
on variables.tf line 17, in variable "vpc_cidrs_public":
17: type = "list"
Terraform 0.11 and earlier required type constraints to be given in quotes,
but that form is now deprecated and will be removed in a future version of
Terraform. To silence this warning, remove the quotes around "list" and write
list(string) instead to explicitly indicate that the list elements are
strings.
(and 6 more similar warnings elsewhere)
Error: Reserved argument name in module block
on main.tf line 141, in module "consul_aws":
141: count = "${var.consul_servers}"
The name "count" is reserved for use in a future version of Terraform.
Error: Reserved argument name in module block
on main.tf line 187, in module "vault_aws":
187: count = "${var.vault_servers}"
The name "count" is reserved for use in a future version of Terraform.
Error: Invalid multi-line string
on outputs.tf line 13, in output "zREADME":
13:
14:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Unterminated template string
on outputs.tf line 13, in output "zREADME":
13:
14:
No closing marker was found for the string.
Error: Invalid multi-line string
on outputs.tf line 14, in output "zREADME":
14:
15:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 15, in output "zREADME":
15:
16:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 16, in output "zREADME":
16:
17:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 17, in output "zREADME":
17:
19:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 19, in output "zREADME":
19:
20:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 20, in output "zREADME":
20:
22:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 22, in output "zREADME":
22:
23:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 23, in output "zREADME":
23:
25:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 25, in output "zREADME":
25:
26:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 26, in output "zREADME":
26:
28:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 28, in output "zREADME":
28:
29:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 29, in output "zREADME":
29:
30:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 30, in output "zREADME":
30:
31:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 31, in output "zREADME":
31:
33:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 33, in output "zREADME":
33:
34:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 34, in output "zREADME":
34:
35:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 35, in output "zREADME":
35:
36:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid multi-line string
on outputs.tf line 36, in output "zREADME":
36:
37:
Quoted strings may not be split over multiple lines. To produce a multi-line
string, either use the \n escape to represent a newline character or use the
"heredoc" multi-line template syntax.
Error: Invalid variable name
on variables.tf line 7, in variable "provider":
7: variable "provider" { default = "aws" }
The variable name "provider" is reserved due to its special meaning inside
module blocks.
Terraform has initialized, but configuration upgrades may be needed.
Terraform found syntax errors in the configuration that prevented full
initialization. If you've recently upgraded to Terraform v0.12, this may be
because your configuration uses syntax constructs that are no longer valid,
and so must be updated before full initialization is possible.
Terraform has installed the required providers to support the configuration
upgrade process. To begin upgrading your configuration, run the following:
terraform 0.12upgrade
To see the full set of errors that led to this message, run:
terraform validate
user@MacBookPro13 terraform-aws %
The text was updated successfully, but these errors were encountered:
I'm wondering if this:
https://github.com/hashicorp/vault-guides/tree/master/operations/provision-vault/best-practices/terraform-aws
or this is a better place to start:
https://github.com/hashicorp/terraform-aws-vault
Apart form the upgrade to .12 being needed, it looks like a few variables names are being used that aren't allowed now, like 'provider'.
The text was updated successfully, but these errors were encountered: