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

link to reference doc page: https://docs.aws.amazon.com/cdk/api/latest/docs/aws-lambda-python-readme.html

describe your issue:

The docs refer to lambda.PythonFunction when that is a part of the aws-lambda-python mo

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

Currently, when outputting log events, any words with substring "ERR" or other fatal codes or warning codes will be shown with color. We should fix this.

e.g. "2 out of 26 resources could not be estimated because they don't have a price or Infracost does not yet support them (https://www.infracost.io/docs/supported_resources)"

Debug level logging could show the resource addresses.

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