How can you ignore data resources in a terraform plan not running against the real aws infrastructure? - terraform

Question

I would like to run a 'terraform plan' for validation that doesn't run against the real aws infrastructure.
My provider configuration for this test is:
provider "aws" {
region = "eu-central-1"
access_key = "mock_access_key"
secret_key = "mock_secret_key"
skip_credentials_validation = true
skip_region_validation = true
skip_requesting_account_id = true
skip_metadata_api_check = true
s3_force_path_style = true
endpoints {
apigateway = "http://localhost:4566"
cloudformation = "http://localhost:4566"
cloudwatch = "http://localhost:4566"
dynamodb = "http://localhost:4566"
es = "http://localhost:4566"
firehose = "http://localhost:4566"
iam = "http://localhost:4566"
kinesis = "http://localhost:4566"
lambda = "http://localhost:4566"
route53 = "http://localhost:4566"
redshift = "http://localhost:4566"
s3 = "http://localhost:4566"
secretsmanager = "http://localhost:4566"
ses = "http://localhost:4566"
sns = "http://localhost:4566"
sqs = "http://localhost:4566"
ssm = "http://localhost:4566"
stepfunctions = "http://localhost:4566"
sts = "http://localhost:4566"
}
}
Here is a small terraform code example.
# terraform code
data "aws_caller_identity" "current" {}
resource "aws_iam_role" "iam_for_lambda" {
name = "lambda-role-name"
inline_policy {
name = "sts"
policy = jsonencode({
Version = "2012-10-17"
Statement = [
{
Action = ["sts:AssumeRole"]
Effect = "Allow"
Resource = "arn:aws:iam::${data.aws_caller_identity.current.id}:role/myrole"
},
]
})
}
}
Everything works as expected except the data resources (from the terraform aws provider). At the moment, terraform is trying to resolve the data resources in the plan and aborts the plan with the following error message.
module.moduletest.data.aws_caller_identity.current: Still reading... [20s elapsed]
╷
│ Error: reading STS Caller Identity
│
│ with module.moduletest.data.aws_caller_identity.current,
│ on ../data.tf line 2, in data "aws_caller_identity" "current":
│ 2: data "aws_caller_identity" "current" {}
│
│ RequestError: send request failed
│ caused by: Post "http://localhost:4566/": dial tcp 127.0.0.1:4566: connect: connection refused
How can you mock the data resources - lookups on aws resources? Are there any additional settings in my provider config necessary?
EDIT
Currently the AWS config are set via environment variables.
export AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
export AWS_SECRET_ACCESS_KEY=wJalxxxxEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
export AWS_DEFAULT_REGION=eu-central-1