#atlantis (2022-03)

atlantis

Discuss the Atlantis (<http://runatlantis.iorunatlantis.io>)

**Archive: ** https://archive.sweetops.com/atlantis/

2022-03-17

Igor avatar

@Erik Osterman (Cloud Posse) I seem to recall you guys used to run your version of Atlantis as a CI job instead of running it standalone. Are you still doing that, or did that pattern die out?

jose.amengual avatar
jose.amengual

that died

jose.amengual avatar
jose.amengual

and it was an ECS container that run atlantis

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Yea, we’re not maintaining that fork

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

@jose.amengual recently was able to help get our patch into the atlantis core, so it’s not needed anymore

Igor avatar

Are you guys still using Atlantis, or have you switched to one of the paid TACOs?

jose.amengual avatar
jose.amengual

spacelift

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Ya, Cloud Posse is focused right now on Spacelift

1
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/terraform-spacelift-cloud-infrastructure-automation

Terraform module to provision Spacelift resources for cloud infrastructure automation

2022-03-20

2022-03-22

2022-03-24

Jonás Márquez avatar
Jonás Márquez

Hello everyone! Is someone using Vault from Atlantis? I have Atlantis in a Docker container on an EC2 Instance in AWS, in the EC2 instance I have configured the Vault agent and mounted the vault-token in the Atlantis container, I am trying access Vault from Terraform with the Vault provider as follows:

provider "vault" {
  skip_tls_verify = true
  address = "https://<IP-ADDRESS>:8200/"
  token = "~/.vault-token"
}

but when I do the Pull Request it gives me the following error:

running "/usr/local/bin/terraform plan -input=false -refresh -out \"/home/atlantis/.atlantis/repos/TEST_PROYECT/test-atlantis-repo/44/default/default.tfplan\"" in "/home/atlantis/.atlantis/repos/TEST_PROJECT/test-atlantis-repo/44/default": exit status 1
╷
│ Error: Error making API request.
│ 
│ URL: GET https://<IP-ADDRESS>:8200/v1/auth/token/lookup-self
│ Code: 400. Errors:
│ 
│ * error performing token check: failed to look up namespace from the token: no namespace
│ 
│   with provider["registry.terraform.io/hashicorp/vault"],
│   on main.tf line 8, in provider "vault":
│    8: provider "vault" {

Namespaces are only used for Vault Enterprise and this is not the case, has anyone been able to implement it? thanks!

jose.amengual avatar
jose.amengual

Atlantis is a tf wrapper

jose.amengual avatar
jose.amengual

it runs the terraform binary

jose.amengual avatar
jose.amengual

so if you run the TF manually on the Atlantis instance it should work there first before

jose.amengual avatar
jose.amengual

if it works in terraform it will work in Atlantis

Adam Blackwell avatar
Adam Blackwell

@Jonás Márquez were you able to figure this out? We’re looking at using the same provider.

2022-03-31

jose.amengual avatar
jose.amengual

Hello guys!!! I’m one of the Atlantis maintainers and I just wanted to let you know that we just released a fix for the VCS status issue some of you have reported on our dev image docker pull [ghcr.io/runatlantis/atlantis:dev](http://ghcr.io/runatlantis/atlantis:dev) Please test it and and report back, Thanks.

2
joshmyers avatar
joshmyers

ah nvm, dev.

joshmyers avatar
joshmyers

Whats different with the dev tag/branch?

joshmyers avatar
joshmyers

Does this track current master?

jose.amengual avatar
jose.amengual

we are going to make it more obvious soon but dev is going be changed to something like prerelease

jose.amengual avatar
jose.amengual

and it will track master

jose.amengual avatar
jose.amengual

and we will give it a month or two to make a base release

jose.amengual avatar
jose.amengual

so we have time for people to try the new changes

    keyboard_arrow_up