PePe Amengual
PePe Amengual
is this still happening with `v0.19.8`?
We will be working on bringing that feature back since it fixes a number of issues, still work in progress
Backend configs do not support interpolation in terraform but the provider does. https://registry.terraform.io/providers/hashicorp/aws/latest/docs#assume-role
I understand but this is not a function of atlantis, this is how terraform is used. you will have to run TF something like this : ``` terraform init -var-file=staging-us-west-2.tfvars...
What are the repo structure and the module instantiation used? a more detailed example could help to understand the feature
so this only works when the `source =` is relative to the checked out repo not when the `source = cloudposse/vpc/aws` which is the terraform registry ?
is this still happening with `v0.19.8`?
is this still happening with `v0.19.8`?
I think atlantis has been in production for years, I believe the 1.0.0 release is just a number, not an actual representation of where atlantis is. What do you think...
locking db as you mentioned was merged yesterday and that will enable autoscaling. the next nonissue but improvement is to maybe use the locking table to find out IF there...