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](

The issue #52359 was fixed and merged into develop, but no further steps have been taken to bring the changes to the master branch; the bug is still present in the latest version.

https://docs.saltstack.com/en/latest/topics/development/git/index.html states develop as the main development branch, but [https://docs.s

Add memory optimised Graviton2 instance type

• 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.

For example-

infracost/infracost:1.0.1-tf0.12.26, infracost/infracost:1.0.1-tf0.13.1

Hi, I just created a new environment (test2) for my app, and now I’m trying to deploy a service to that environment but it fails.

Just for context, I’m attempting to use a monorepo setup:

• My apps (services) are in /apps/
• My copilot manifests etc are in /infrastructure/copilot/
• I always run copilot from /infrastructure/
• Each manifest has an image property that points to

Garbage collection works by listing everything with the gc-tag. In a busy cluster, we really want that filter to happen server-side and ideally using an index of some sort.

That means we should use a Kubernetes label, not an annotation.

I think this will require a two-step migration plan (write both but continue to read annotation; release; drop support for annotation; release).

Because having to type the whole commands is a pain!