#terraform-aws-modules - August 2021

hey guys, how do I get atlantis to point to nothing (i.e. plan to destroy everything)
we use export TF_CLI_INIT_FROM_MODULE=git::<https://github.com/>....

with

source_up
use envrc
use terraform
use tfenv

removing from here

Hello. On terraform 1.0.4, the terraform-aws-config is raising this issue

│   on .terraform/modules/aws_config_storage.storage.this/versions.tf line 2, in terraform:
│    2:   required_version = ">= 0.12.0, < 0.14.0"
│
│ Module module.aws_config_storage.module.storage.module.this (from git::<https://github.com/cloudposse/terraform-null-label.git?ref=tags/0.19.2>) does not support Terraform
│ version 1.0.4. To proceed, either choose another supported Terraform version or update this version constraint. Version constraints are normally set for good reason, so
│ updating the constraint may lead to other errors or unexpected behavior.

Anyone had the same issue ?

Hi everyone. Is there a guide on how to use https://github.com/cloudposse/terraform-aws-config ?
I'm started with https://github.com/cloudposse/terraform-aws-config/tree/master/examples/cis, but getting some errors like The argument "role_arn" is required, but no definition was found.

We have just released a new version of null-label, which has triggered updates to virtually all of our Terraform modules.
• Please wait to update your modules until you have a reason to. This is not a bugfix release. It has some new features to support "tenants" that are only needed by a very few people. It has a new feature to deconflict tags with the new AWS provider's default_tags , so if you hare having problems with that, then that is a reason to update your root module to use the new context.tf. Otherwise, you can wait, and probably should wait, so we can fix any bugs that may surface.
• The update triggered automatic updates of modules that were in a pre-release state because they were not backward compatible and were going to have another round of breaking changes published. Unfortunately, the automatic updates triggered normal releases (not pre-releases) that got pushed to the Terraform registry. These new releases remain incompatible and should not be adopted. Sorry for the false alert.
• As a general rule we work hard to preserve backward compatibility and we prominently note when there is a breaking change. If you find breaking changes without mention in the release notes, that is definitely a problem. Right now, because of the quantity of changes, it will take us a while to triage and fix whatever comes up, so please simply roll back to an earlier version if the current version is not working for you.

It doesn't seem like it's possible to view Bridgecrew security analysis results on pull requests any more. I submitted https://github.com/cloudposse/terraform-aws-rds-cluster/pull/119 and clicking the Bridgecrew link:
https://www.bridgecrew.cloud/projects?repository=cloudposse/terraform-aws-rds-cluster&branch=119_ignore-admin-creds&runId=latest
I was prompted to login, I used by Github credentials and get redirected to this page:
https://www.bridgecrew.cloud/organization
Which simply asks me to set a permanent organisation name.

Hi team! Nice to be here with you.
I’m facing this issue https://github.com/cloudposse/terraform-aws-elasticsearch/issues/57
Do you have any suggestion to resolve it?