-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Terragrunt Aplly-ALL doesnt work multiple errors #28
Comments
|
The first error is the named validation problem. Second Elb Module Terraform problem |
First assumption is that you have named your DB instance starting with the letter. Text labels are passed into module as argument ( ALB is failing because you have to specify "At least two subnets in two different Availability Zones must be specified". If you have edited this manually, make sure you set it correctly. Normally VPC resources like subnets are created across all available AZs. If problem persists, please share a link to your blueprint by email. |
Yes, but we can't manage Az in the cloud craft. It is something that scripts (module.tf) do during the import. Name prefix is
name_prefix is not part of terragrunt configuration |
Hi! I still struggling with this error.
And the weirdest one is ALB doesn't work
I'm trying to fix parameter name by fix name |
RDS identifier is using wrong characters inside but since that value is used to create some other resources you need to update it to satisfy these error messages - "only lowercase alphanumeric characters and hyphens", "first character ... must be a letter". ALB error is probably related to a missing
If not, please show |
Yes, there are no
########################################################### View all available inputs for this module:https://registry.terraform.io/modules/terraform-aws-modules/alb/aws/5.1.0?tab=inputs########################################################### The resource name and Name tag of the load balancer.type: stringname = "guided-lemur" } |
I have fixed RDS issue by removing "-" sign from the name. but this error a little bit weird :
|
Add It was not specified automatically, because your ALB was not belonging to a VPC in a diagram, I suppose. |
It is belonging to the VPC... it just doesn't generate it Can you also provide how to add these values they are missing also . I checked old version
I have this dependencies: dependencies {
|
it is an example - https://app.cloudcraft.co/view/f8abab63-0007-4ea2-8ea8-b9186d3259f1?key=iBtyR4AsIr9jWfy-sJARUg it doesn't add a subnet to ELB my blueprint is - blueprint/0b356102-1692-478a-a0fa-901c9323ab1f |
RDS name_prefix issue fixed after setting name to "mysql" without any symbols instead of "mysql-rds". |
A similar issue is when a security group is named Pretty weird requirements by AWS. |
After run "terragrunt apply-all" but load balancer doesn't have target groups/listeners created and so no instances are load-balanced |
That is because a lot of important information is not available in cloudcraft and user has to add it themself manually. Here you can see an example of ALB module usage - https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/examples/complete-alb/main.tf |
Thanks for your replay. I will chack
…On Wed, May 13, 2020 at 2:36 PM Anton Babenko ***@***.***> wrote:
That is because a lot of important information is not available in
cloudcraft and user has to add it themself manually.
Here you can see an example of ALB module usage -
https://github.com/terraform-aws-modules/terraform-aws-alb/blob/master/examples/complete-alb/main.tf
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACGJNZUXXYYOPEEH27QNUSTRRMHFBANCNFSM4LTGL5JQ>
.
|
It doesn't appear that modules covers the use case of using named or aliased security groups, yet. Also, as most people are designing small architectures right now, does it make sense to just create the subnets for them, baked into the terraform? Some strategies:
|
The text was updated successfully, but these errors were encountered: