-
-
Notifications
You must be signed in to change notification settings - Fork 355
ATLANTIS_ATLANTIS_URL not correctly picked up from atlantis.fqdn #377
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
Comments
Hello, This local env should do the job atlantis_url = "https://${try(coalesce(
try(var.atlantis.fqdn, null),
module.alb.route53_records["A"].fqdn,
module.alb.dns_name,
), "")}" On my tests I'm using the creation of the ACM and the record, and it works like a charm. If you need a code example with these, please let me know. |
When using an existing ALB, module.alb isn't fully populated, and referencing the Route 53 records fails. The error is caught by the top-level try, leaving atlantis_url empty. With this change, wrapping each reference to module.alb in a try, var.atlantis.fqdn is used even when using an existing ALB. Fixes terraform-aws-modules#377.
When using an existing ALB, module.alb isn't fully populated, and referencing the Route 53 records fails. The error is caught by the top-level try, leaving atlantis_url empty. With this change, wrapping each reference to module.alb in a try, var.atlantis.fqdn is used even when using an existing ALB. Fixes terraform-aws-modules#377.
When using an existing ALB, module.alb isn't fully populated, and referencing the Route 53 records fails. The error is caught by the top-level try, leaving atlantis_url empty. With this change, wrapping the reference to module.alb.route53_records in a try, var.atlantis.fqdn is used even when using an existing ALB. Fixes terraform-aws-modules#377.
When using an existing ALB, module.alb isn't fully populated, and referencing the Route 53 records fails. The error is caught by the top-level try, leaving atlantis_url empty. With this change, wrapping the reference to module.alb.route53_records in a try, var.atlantis.fqdn is used even when using an existing ALB. Fixes terraform-aws-modules#377.
resolved in #379 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
I am initializing the terraform-aws-atlantis module with the DNS records for the ALB manually configured (the domain we want is managed outside of Route53). To ensure
local.atlantis_url
is correctly set within the module, I am trying to setvar.atlantis.fqdn
to the correct URL; however, when I runterraform plan
, the env variable forATLANTIS_ATLANTIS_URL
is set to justhttps://
.I have worked around this issue by defining another env variable with
ATLANTIS_ATLANTIS_URL => url we want
, but this is not ideal as AWS squashes the two env variables together, resulting interraform plan
always indicating that there is a change to made despite there not being a code change.Relevant LOC:
terraform-aws-atlantis/main.tf
Line 4 in f983fd8
Versions
Module version [Required]: 4.0.3
Terraform version: 1.6.3
Reproduction Code [Required]
Expected behavior
Env variable
ATLANTIS_ATLANTIS_URL
should be set to "https://foobar.com"Actual behavior
Plan output (only relevant parts included)
The text was updated successfully, but these errors were encountered: