curved-autumn-58528
07/11/2022, 3:21 PMwitty-tiger-63221
07/12/2022, 11:06 AMechoing-plumber-53799
07/12/2022, 10:17 PMpolite-vr-31842
07/30/2022, 6:25 AMmillions-market-56318
08/12/2022, 2:06 PMsync-usage-file
option helps them out here by providing a usage file with default values(mostly 0s). Do you see a way this could be improved by somehow providing reasonable defaults, something like the contents of the infracost-usage-example.yml
. Perhaps somehow leveraging that file. Do you see any value here?
2, The user already has their estimate and usage file but they add a new resource thatβs type matches an already existing one in the configuration. When using the sync-usage-file
option, could option leverage the already existing usage estimates for the existing resource type for the same type of resource that was just added? Again, do you think there is any value here?
Thanks!curved-autumn-58528
08/19/2022, 3:05 PMhappy-needle-44794
08/23/2022, 2:17 PMcrooked-daybreak-55253
08/30/2022, 1:20 PMbest-apartment-84744
09/21/2022, 6:51 AMterraform {
required_providers {
confluent = {
source = "confluentinc/confluent"
version = "1.3.0"
}
}
}
Iβm a bit rusty with Golang, but if its not too silly, Iβm prepared to create a card and have a go with it.little-author-61621
colossal-table-21540
10/13/2022, 1:28 PMcolossal-table-21540
10/13/2022, 1:31 PMcolossal-table-21540
10/13/2022, 1:31 PM-ββββββββββββββββββββββββββββββββββ
-
-The following projects have no cost estimate changes: infracost/infracost/cmd/infracost/testdata/terraform_v0.14_nochange_plan.json
-Run the following command to see their breakdown: infracost breakdown --path=/path/to/code
-
-ββββββββββββββββββββββββββββββββββ
-
-
-</details>
-
+π° Infracost estimate: monthly cost will not change
+<table>
+ <thead>
+ <td>Project</td>
+ <td>Previous</td>
+ <td>New</td>
+ <td>Diff</td>
+ </thead>
+ <tbody>
+ <tr>
+ <td>infracost/infracost/cmd/infraco...aform_v0.14_nochange_plan.json</td>
+ <td align="right">$40.56</td>
+ <td align="right">$40.56</td>
+ <td>$0</td>
+ </tr>
+ </tbody>
+</table>
+
+<details>
+<summary><strong>Infracost output</strong></summary>
+
+```
+ββββββββββββββββββββββββββββββββββ
+
+The following projects have no cost estimate changes: infracost/infracost/cmd/infracost/testdata/terraform_v0.14_nochange_plan.json
+Run the following command to see their breakdown: infracost breakdown --path=/path/to/code
+
+ββββββββββββββββββββββββββββββββββ
+
+```
+</details>
+
+
--- FAIL: TestOutputFormatGitHubCommentNoChange (0.06s)
--- FAIL: TestOutputFormatGitHubCommentNoChange/HCL (0.06s)stocky-salesmen-15167
10/14/2022, 8:02 AMβ― INFRACOST_LOG_LEVEL=debug go test -v -cover ./internal/providers/terraform/aws/fsx_windows_file_system_test.go
=== RUN TestFSXWindowsFS
=== PAUSE TestFSXWindowsFS
=== CONT TestFSXWindowsFS
=== RUN TestFSXWindowsFS/HCL
level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_file_system_ssd SSD storage, using the first productβ
testutil.go202 Unexpected log write. To capture logs remove t.Parallel and use GoldenFileOptions { CaptureLogs = true }: level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_file_system_ssd SSD storage, using the first productβ
level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_system_ssd SSD storage, using the first productβ
testutil.go202 Unexpected log write. To capture logs remove t.Parallel and use GoldenFileOptions { CaptureLogs = true }: level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_system_ssd SSD storage, using the first productβ
=== RUN TestFSXWindowsFS/Terraform_CLI
level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_file_system_ssd SSD storage, using the first productβ
testutil.go202 Unexpected log write. To capture logs remove t.Parallel and use GoldenFileOptions { CaptureLogs = true }: level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_file_system_ssd SSD storage, using the first productβ
level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_system_ssd SSD storage, using the first productβ
testutil.go202 Unexpected log write. To capture logs remove t.Parallel and use GoldenFileOptions { CaptureLogs = true }: level=warning msg=βMultiple products with prices found for aws_fsx_windows_file_system.my_system_ssd SSD storage, using the first productβ
--- FAIL: TestFSXWindowsFS (6.62s)
--- FAIL: TestFSXWindowsFS/HCL (0.65s)
--- FAIL: TestFSXWindowsFS/Terraform_CLI (5.97s)
FAIL
coverage: [no statements]
FAIL command-line-arguments 7.180s
FAILWhere would I need to start debugging that? Thanks, Johannes
stocky-magazine-90066
11/13/2022, 11:07 AMstocky-magazine-90066
11/16/2022, 1:42 PMstocky-salesmen-15167
11/25/2022, 10:46 AMmysterious-teacher-68276
11/25/2022, 10:47 AMmysterious-teacher-68276
11/25/2022, 10:48 AMearly-queen-42970
stocky-salesmen-15167
11/25/2022, 7:02 PMbrave-fireman-95738
01/06/2023, 8:52 AMechoing-caravan-39531
01/24/2023, 12:10 AMstocky-magazine-90066
02/06/2023, 1:38 PMfunc getLambdaFunctionRegistryItem() *schema.RegistryItem {
return &schema.RegistryItem{
Name: "aws_lambda_function",
Notes: []string{"Provisioned concurrency is not yet supported."},
ReferenceAttributes: []string{"function_name"},
CoreRFunc: NewLambdaFunction,
}
}
I then added this to a new resource for provisioned concurrency
func getLambdaProvisionedConcurrencyConfigRegistryItem() *schema.RegistryItem {
return &schema.RegistryItem{
Name: "aws_lambda_provisioned_concurrency_config",
RFunc: NewLambdaProvisionedConcurrencyConfig,
ReferenceAttributes: []string{"aws_lambda_function.function_name"},
}
}
Am I missing something ? Because I'm unable to access this from within the new provisioned concurrency resource. It's empty!!
Any help would be appreciated, I looked at the example here
Example terraform below.
# Add example resources for LambdaProvisionedConcurrencyConfig below
resource "aws_lambda_provisioned_concurrency_config" "lambda_provisioned_concurrency_config" {
function_name = aws_lambda_function.lambda.function_name
provisioned_concurrent_executions = 50
qualifier = aws_lambda_function.lambda.version
}
resource "aws_lambda_function" "lambda" {
function_name = "lambda_function_name"
role = "arn:aws:lambda:us-east-1:account-id:resource-id"
handler = "exports.test"
filename = "function.zip"
runtime = "nodejs12.x"
architectures = ["arm64"]
memory_size = 512
}
white-airport-8778
version: 0.1
projects:
- path: my-whatif.json
name: development
arm_location: us-east-1
arm_resource_group_name: myRG
# or something like this so the same param names to the ARM CLI can be defined?
arm:
location: us-east-1
resource_group_name: myRG
stocky-salesmen-15167
03/14/2023, 8:11 AMfaint-mouse-18716
03/28/2023, 12:07 AMazurerm_lb_rule
resource. If the rule is attached to an azurerm_lb
load balancer with the Basic
SKU this is a free resource, but if itβs attached to a Standard
SKU it has an associated cost.
The original issue requesting support for these load balancers called this out, but it looks like it was missed in the the initial implementation. π§΅flat-apartment-2312
06/03/2023, 6:50 PMripe-answer-8822
08/25/2023, 1:27 PMaws_kinesis_streams
https://github.com/infracost/infracost/issues/2510
I have read and followed the guide on how to add a cost component and that bit works fine until I try to add 2 resources, 1 of Provisioned
and 1 of On_Demand
. Given the pricing API results look like this, I am really struggling to work out how to structure my cost component to accept both stream types. In the example it seemed quite trivial since the transfer family resource shared the same naming scheme (on operation
)
service | productFamily | data | operation | usagetype
---------------+-----------------+------+----------------------------------+------------------------------------
AmazonKinesis | Kinesis Streams | | ConsumerHour | EnhancedFanoutHour
AmazonKinesis | Kinesis Streams | | EnhancedFanoutDataRetrieval | ReadBytes
AmazonKinesis | Kinesis Streams | | LongTermRetentionByteHrs | LongTermRetention-ByteHrs
AmazonKinesis | Kinesis Streams | | LongTermRetentionDataRetrieval | LongTermRetention-ReadBytes
AmazonKinesis | Kinesis Streams | | OnDemandDataIngested | OnDemand-BilledIncomingBytes
AmazonKinesis | Kinesis Streams | | OnDemandDataRetrieval | OnDemand-BilledOutgoingBytes
AmazonKinesis | Kinesis Streams | | OnDemandEFODataRetrieval | OnDemand-BilledOutgoingEFOBytes
AmazonKinesis | Kinesis Streams | | OnDemandExtendedRetentionByteHrs | OnDemand-ExtendedRetention-ByteHrs
AmazonKinesis | Kinesis Streams | | OnDemandLongTermRetentionByteHrs | OnDemand-LongTermRetention-ByteHrs
AmazonKinesis | Kinesis Streams | | OnDemandStreamHr | OnDemand-StreamHour
AmazonKinesis | Kinesis Streams | | PutRequest | PutRequestPayloadUnits
AmazonKinesis | Kinesis Streams | | shardHourStorage | Extended-ShardHour
AmazonKinesis | Kinesis Streams | | shardHourStorage | Storage-ShardHour
Do I just make separate components in this case, or is there a fancy way to get both stream types working in the same one, if so is there any examples in the code where this has been done before?
Apologies if its common knowledge to create 2 components for this situation, Problems with this being my first 1!