#atlantis (2021-12)
Discuss the Atlantis (<http://runatlantis.io | runatlantis.io>) |
**Archive: ** https://archive.sweetops.com/atlantis/
2021-12-04
Hi all I am in process of setting up AWS infra for brand new organisation and I was wondering if there are any best-practices related to deploying atlantis to multi-account environments? Would I deploy an atlantis instance in each AWS account, group of accounts or one for everything? Initially, the organisation will be rather basic, but with potential to grow in the future. I am going to have all the basic fundamental OU in my AWS org, and maybe a couple of workloads: https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/basic-organization.html
The following example incorporates a security tooling environment for common security services, a second workload, and support for sandbox and development environments. Additions include:
I suppose I found the answer to my question: https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/deployments-ou.html
The Deployments OU contains resources and workloads that support how you build, validate, promote, and release changes to your workloads.
2021-12-07
Any ideas what requirements are around removing “Refresh” lines from Atlantis output? Specifically around versions >= 0.14.X
A load of PRs
Fixes #1306 Since Terraform 0.14.0 there are no separator between refreshing plan and the plan. This strategy is to find the last line with "Refreshing state…" and remove it with all of…
Since Terraform 0.14.0 there are no separator between refreshing plan and the plan.
Am using terragrunt workflow with TF 0.14.6 and still getting refresh output
Note that I’m not using Atlantis to manage the version of Terraform for a given project https://github.com/runatlantis/atlantis/blob/38cf7b014137637c065513b2077eca0c8ef43541/server/core/runtime/plan_step_runner.go#L291
Terraform Pull Request Automation. Contribute to runatlantis/atlantis development by creating an account on GitHub.
Cloud Posse doesn’t manage runatlantis org so we cannot merge those PRs
@joshmyers I believe atlantis has their own slack. Have you tried there ?
The PRs have all already gone in
Just having a poke around the code https://github.com/runatlantis/atlantis/blob/38cf7b014137637c065513b2077eca0c8ef43541/server/core/runtime/plan_step_runner.go#L290-L313
Terraform Pull Request Automation. Contribute to runatlantis/atlantis development by creating an account on GitHub.
ohh ok I see
Cool, I’ll ask in the atlantis Slack (if can find it)
I thought you needed those merged. My apologies
Is there an Atlantis Slack?
@hamstah: as in it’s “not officially supported”
Yeah, have asked in there but seems pretty dead
Anyone got “Refresh” not showing in Atlantis plans?
hi
lol
2021-12-21
@Andriy Knysh (Cloud Posse) it took 3 years, 2 closed PRs, and 3 different people, but your PR for Atlantis allowlists finally made it!!!!! Thanks @jose.amengual https://github.com/runatlantis/atlantis/pull/1694
Summary Configure permissions by GitHub team, with a list of teams and commands they are permitted to use. Usage atlantis server –gh-team-allowlist "myteam:plan, secteam:apply" Backgroun…
yes, @jose.amengual showed it to me
Summary Configure permissions by GitHub team, with a list of teams and commands they are permitted to use. Usage atlantis server –gh-team-allowlist "myteam:plan, secteam:apply" Backgroun…
Important Note Users are advised to upgrade to release 0.9.0.2 The gh-team-whitelist feature in this release has known deficits and should not be relied on. Users are advised to upgrade to release …
thanks @jose.amengual for taking over