|Discuss the Atlantis (<http://runatlantis.io||runatlantis.io>)|
**Archive: ** https://archive.sweetops.com/atlantis/
i made a pull request that parhaps fixes the problem
I updated to 0.8.1 running on fargate, and authentication fails for me on the app user in BitBucket. @nutellinoit Have you given the new version a shot yet? Are things working for you?
I tried one pull request this morning and everything was working , I did not try without approving the pull tho
@nutellinoit You didn’t have to update anything with the bitbucket app user?
I will try tomorrow morning with other pull requests
it’s 22:52 in Italy
Thanks, must be something with my setup, I jumped a few versions
Okay, figured it out, I now need to use the username of the actual BitBucket user, instead of the app name as it previously was configured
is there a way to pass the region for the aws provider directly to whatever modules the ecs-atlantis depends on?
I’ve noticed that it asks twice for
provider.aws.region so I am assuming region is not passed alongside to dependencies.
Acquiring state lock. This may take a few moments... provider.aws.region The region where AWS operations will take place. Examples are us-east-1, us-west-2, etc. Default: us-east-1 Enter a value: us-east-2 provider.aws.region The region where AWS operations will take place. Examples are us-east-1, us-west-2, etc. Default: us-east-1 Enter a value: us-east-2
not a big deal, but I wonder if this is expected
basically it seems that var.region ain’t passed here: https://github.com/cloudposse/terraform-aws-ecs-atlantis/blob/master/main.tf#L79
@marc we did not test it in this scenario. We have ENV var for region defined in the Dockerfile(s) https://github.com/cloudposse/testing.cloudposse.co/blob/master/Dockerfile#L20
Example Terraform Reference Architecture that implements a Geodesic Module for an Automated Testing Organization in AWS - cloudposse/testing.cloudposse.co
so it always has the region
ah, good to know
but we will be converting it to TF 0.12, and fix that too