I'm trying to use nbering/terraform-provider-ansible by placing it in ~/.terraform.d/plugins/linux_amd64/terraform-provider-ansible, but terraform init never seems to actually find it (NB this works fine in 0.12.x). Why is that?

Can 0.13 actually load plugins from local file-system directories (as [described in the documentation](

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

during any terragunt action it will show this line

> terragrunt plan
2020/06/08 12:12:26 Running command: terraform --version

and doesn't show the terraform version. this makes it hard to debug some language issues because I'm not sure what terragrunt is actually running. should this be printing a version string?

• Dockerfile include terraformer version with all providers
• Script install providers on start container
• Manual in README about docker run command, include volume mounts for outputs, credentials and etc.

目前备份存储只支持oss,s3,azure三种云端存储方案，希望增加本地存储方案（Ceph,nfs,nas）

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and

There's a formatting specification for Tag Keys and Values. One issue with applying some changes is that you are disallowed from using certain characters (notably the ,) in a Tag Value, and this is not being caught by tflint currently.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html#w2ab1c25c10d254c13c17

Hi, great project. I'd like to make a request. Right now, to exclude rules, you have to modify the code to "a comment containing tfsec:ignore:<RULE> to the offending line in your templates", per the README. It would be very useful if we could do this via CLI args as well, for assessment purposes.

PR o'clock

Description

1. Add ingress rule to workers and cluster security groups to allow Fargate pods to communicate with EC2 nodes
2. Allow EKS Fargate profiles to be created via input eks_fargate_profiles = [...]. This also creates an IAM role for pod execution and extends the aws-auth ConfigMap.

Checklist

• CI tests are passing
• README.md has been updated aft

Of the learning environments that leverage Ansible, very few are using roles. This can make porting Ansible playbooks across learning environments more difficult. To fix this, Ansible-using learning environments need to be refactored (where possible) to use an Ansible role.

Check to confirm CloudTrail is configured for multi-region.

CloudFormation - IsMultiRegionTrail: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudtrail-trail.html

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do n

Blast Radius , when launched in --serve mode, does some pretty weak error reporting, and does nothing to help users resolve problems. It asks the user to look into several possible issues, rather than checking itself...

To observe the current (undesired) behavior, run Blast Radius in an empty directory:

[...]$ mkdir tmp
[...]$ cd tmp
[...]$ blast-radius --serve

A short