-
### Terraform Core Version
1.9.0
### AWS Provider Version
5.62.0
### Affected Resource(s)
* aws_quicksight_folder
### Expected Behavior
No change
### Actual Behavior
When mu…
-
## Description
I've upgraded the `"terraform-aws-modules/eks/aws//modules/karpenter"` from `20.0` to `20.24.0`, and then upgraded the Helm chart version from `0.37.0` to `1.0.1`.
After applying …
-
## Description
When setting up a new cluster using the `eks auth module` with `manage_aws_auth_configmap = true` , I get the following error message.
```
Error: Have got the following error wh…
-
### Terraform Core Version
1.9.0
### AWS Provider Version
5.63.1
### Affected Resource(s)
aws_sagemaker_endpoint
### Expected Behavior
When Terraform apply attempts to call `Updat…
-
### Terraform Core Version
1.7.0
### AWS Provider Version
5.33.0
### Affected Resource(s)
```
https://registry.terraform.io/providers/hashicorp/aws/4.40.0/docs/resources/codebuild_project.html#e…
-
### Description
The newly added data sources `aws_rds_cluster_parameter_group` and `aws_db_parameter_group` do not return parameters. they're effectively useless in the current state as they are now.…
-
### Description
This resource would allow practitioners to manage AWS Lambda function recursion configurations via Terraform.
### Requested Resource(s) and/or Data Source(s)
- `aws_lambda_fun…
jar-b updated
2 weeks ago
-
### Description
I noticed that default tags set for AWS Provider are not created for the Amazon Connect instance. Also, it is not possible to manage instance tags via Terraform
### Affected Resource…
-
### Terraform Core Version
1.7.3
### AWS Provider Version
4.67.0
### Affected Resource(s)
aws_lambda_function
### Expected Behavior
1) Run terraform plan and apply.
2) Completes successfully a…
-
Terraform for AWS keeps Lambda versions from previous deployments. These Lambda versions may be attached to a VPC and a Security Group, and if this VPC or Security Group is to be removed in the future…