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

Description
I get the following warnings once a minute:

2020-06-23 23:11:13,900 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt/master/roots/mtime_map: /srv/salt/a/b/c/ifcfg-eth0:0:1533517049.0

2020-06-23 23:11:13,901 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt

InstanceType.of(InstanceClass) ENUM does not support C6G family. https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-ec2/lib/instance-types.ts.

Use Case

Utilizing ENUM as best practice rather than string literal to define EC2 instance type in CDK stack.

Proposed Solution

Add C6G to ENUM - InstanceClass.COMPUTE6_GRAVITRON

`COMPUTE6_GRAVITRON = 'c6g

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

1. Currently when I run infracost outside of a terraform directory, I get the error shown below, I think I prefer to see the help screen by default vs an error; terraform, pulumi, gh do this by default.

⠙ Calculating costs… ERROR
ERROR Error: No configuration files

Perhaps we can detect that infracost is not being run inside a terraform dir, and output the help text instead of

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!

Found a bug in Collectors (#50). All collectors redundantly copied a bug where the Promise was not awaited.

https://github.com/sam-goodwin/punchcard/blob/d476533a032a9dfee9fecfffd7a852744f63d288/packages/punchcard/lib/kinesis/collector.ts#L63-L68

Bug is fixed, but we should make a generic SinkCollector for all types that implement Sink<T>.