[BUG] Terrafrom error content not detected in API
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, docker-compose, python, terraform
- Domain
- api, cloud, infrastructure
Research direction
Start with the Terraform apply failure shown in the Docker Compose logs and the referenced modules/generic-server/resources.tf entry. Trace how the API handles the nonzero Terraform return and captures its output; done means the visible Terraform error is detected and reported instead of producing the generic no-output message.
Written by the indexing model from the issue text.
Description
While I was provisioning AR in AWS I got an error which is not relevant to this issue. I have noticed in docker compose logs that error output was not detected, even though it's clearly visible just above.
attack-range-api | module.networkModule.module.vpc.aws_route.private_nat_gateway[0]: Creating...
attack-range-api | module.networkModule.module.vpc.aws_route.private_nat_gateway[0]: Creation complete after 0s [id=r-rtb-05f56bcf1b19b2a1e1080289494]
attack-range-api | ╷
attack-range-api | │ Error: creating EC2 Instance: operation error EC2: RunInstances, https response error StatusCode: 400, RequestID: 5bb8253a-6c75-419f-bf48-a4b4529a2cf3, api error PendingVerification: Your request for accessing resources in this region is being validated, and you will not be able to launch additional resources in this region until the validation is complete. We will notify you by email once your request has been validated. While normally resolved within minutes, please allow up to 4 hours for this process to complete. If the issue still persists, then open a support case. [https://support.console.aws.amazon.com/support/home?region=us-east-1#/case/create?issueType=customer-service&serviceCode=account-management&categoryCode=account-verification]
attack-range-api | │
attack-range-api | │ with module.attack_range_servers["splunk"].aws_instance.this,
attack-range-api | │ on modules/generic-server/resources.tf line 28, in resource "aws_instance" "this":
attack-range-api | │ 28: resource "aws_instance" "this" {
attack-range-api | │
attack-range-api | ╵
attack-range-api | 2026-02-11 09:29:15,602 - ERROR - attack_range - Terraform apply failed!
attack-range-api | 2026-02-11 09:29:15,602 - ERROR - attack_range - No error output from terraform (return code != 0)
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 417
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from splunk/attack_range
-
On Premise request Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
splunk/attack_range#1428 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
splunk/attack_range#1415 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
splunk/attack_range#1368 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
splunk/attack_range#1366 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
splunk/attack_range#1340 · 1 comment ·
All issues in splunk/attack_range
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·