This message was deleted Infracost Community #contributors

$https://infracost.io logo$

Join Slack

This message was deleted.

# contributors

broad-zoo-34077

07/22/2021, 6:19 PM

This message was deleted.

little-author-61621

07/22/2021, 6:22 PM

It should work for

count

and

for_each

. +1 we should clarify this.

👍 2

damp-ambulance-61372

07/23/2021, 9:33 AM

@little-author-61621 it seems the wildcard char in usage-file is not working with for_each. (tested with

infracost/example-terraform/sample1

aws_lambda_function.hello_world

damp-ambulance-61372

07/23/2021, 9:33 AM

aws_lambda_function.hello_world["hello"] ├─ Requests 0 1M requests $0.00 └─ Duration 0 GB-seconds $0.00 aws_lambda_function.hello_world["hi"] ├─ Requests 0 1M requests $0.00 └─ Duration 0 GB-seconds $0.00

damp-ambulance-61372

07/23/2021, 9:35 AM

Oh sorry my bad it is working ok, but the issue is

--sync-usage-file

is destructive when using with wildcards (both for

for_each

and

count

)

damp-ambulance-61372

07/23/2021, 9:36 AM

it deletes all the wildcard

aws_lambda_function.hello_world[*]

and replaces them with individual

aws_lambda_function.hello_world["hi"]

and

"hello"

with default value

little-author-61621

07/23/2021, 9:38 AM

hmmm that's an interesting issue. I guess in that case it should recognise the wildcards and not overwrite them.

👍 1

damp-ambulance-61372

07/23/2021, 9:59 AM

We should also consider this behavior (having both wildcard and resource) in

--sync-usage-file

logic

damp-ambulance-61372

07/23/2021, 10:57 AM

submitted an issue for

--sync-usage-file

flag behavior: https://github.com/infracost/infracost/issues/875 submitted a PR for clarifying wildcard usage with for_each: https://github.com/infracost/docs/pull/81

🙌 1

5 Views

Open in Slack

Previous Next