#atlantis (2020-07)

On the server, you can run the atlantis version command: https://github.com/runatlantis/atlantis/blob/master/cmd/version.go

ah but i cannot do this since im using a fargate task

I think the easiest way then is to check however you built the docker image running in the fargate task and see if you specify a version.

Otherwise, you can always pull down the image running in your task by SHA, start a shell in it, and run atlantis version

well, yes that’s what im doing too. i ran into an issue today where i built a new image, updated terraform, and realized that fargate had not deployed a new instance when i was trying to use a 1.4.0 feature

i looked around for an easy way to get the version and couldn’t unless i used a custom workflow script which is pretty hackish

i did a force deployment on the ecs service and viola, new 0.14.0 feaeture was now available

doesn’t seem possible, so created this ticket https://github.com/runatlantis/atlantis/issues/1119

put in a pr https://github.com/runatlantis/atlantis/pull/1120

in the ui you can see it

bottom right

oh man, thank you. that’s just wonderful

I do not use the UI but one day I was trying to find the same and someone pointed that at me

and even then trying to find the faded version on the ui took few seconds

perfect.

✗ curl -s <https://atlantis.internal.company.com> | grep -Po '^v.*'
v0.14.0

lol that so not 2020

I saw your PR

that is a better way

he wants it in the /status endpoint but im struggling with figuring out how to access the server information in that endpoint

I use this script:

/**
 * This script is sets up protections over who can run `atlantis apply`
 * commands on our Infra related PRs to update our infra.
 *
 * It is mounted onto the Docker image, and updates to this file can
 * only be pushed to the remote repository by admins.
 */

const { ADMINS } = process.env;
const APPLY_USER = process.env.USER_NAME;

if (!ADMINS) {
  throw Error(
    'Could not find admin user list for determining if this "Apply" command is allowed',
  );
}

if (!APPLY_USER) {
  throw Error('Could not find user running the Apply command');
}

if (!ADMINS.split(',').includes(APPLY_USER)) {
  throw Error(
    `User ${APPLY_USER} is not an admin, and cannot run Atlantis Apply commands`,
  );
}

console.log(`Validated that ${APPLY_USER} is an admin`);

Not sure if that is the best way, but it works until that PR is merged

I forked atlantis and added cloudposse gh-team-whitelist

and I can update and get the new features

we have our own fork of atlantis that let’s us specify that atlantis config to use so that we can have multiple atlantis services work on the same repo

I added that too!!! pretty useful

we have been using the cloudposse feature and it works perfectly

do you think atlantis maintainers would accept the team whitelist feature?

nope

it has been outstanding for a long time

there is a very long discussion about it

they added one feature that is not nearly as complete

i used thi smethod https://github.com/nitrocode/atlantis-terraform-module

basically i have a users file containing github users. if your username is not in it, then you cannot apply.

https://github.com/nitrocode/atlantis-terraform-module/blob/master/atlantis.yaml#L18

yes that is one way I have seen, if Atlantis run exposed more Variables you could do more stuff

by using the cloudposse fork, how often does cloudposse resync with the upstream fork ?

cloudposse/default-backend:0.12

ok this is the fork https://github.com/cloudposse/atlantis

looks like it hasn’t been updated in about 10 months tho

that is why I created my own fork

https://github.com/sonatype/atlantis

oofah, so many forks

so your fork is up to date with lkysow’s repo and has the cloudposse additions ?

yes

and one more addition

for use with multiple atlantis-XXXX.yaml files

so you can use it with multiple servers

amazing

you should put that in your README.md

but right now is 0.13

then we can all start using it xD

I need to pull the latest

if you can automate the sync and merge, that would be even better

I was about to pull the new version to use github apps aythentication

we will

and we are going to security test it

since that is what we do

https://github.com/sonatype-nexus-community/nancy

oh nice