Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Terrafrom error content not detected in API

Open
#1,367 0 comments 0 reactions 0 assignees View on GitHub

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

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from splunk/attack_range

All issues in splunk/attack_range

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.