splunk / splunk/attack_range

[ENH] Allow to retry 2nd build_lab phase in case VPN connection was not configured or ansible failed.

Open
#1,368 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2.6k
Forks
417
PR merge metrics
No merged PRs in 30d

Description

I was able to finishing building 1 phase, then without configured wireguard i started building lab (2nd phase). Naturally, ansible was not able to connect to instances and failed in that case web app was showing it's in progress (hang) and it only allows to Abort. Once aborted the only option is to Destroy env, it would be handy if I could retry 2nd phase from UI.

Steps to reproduce:

  • complete 1st build phase with web app
  • do not configure VPN
  • run 2nd build phase with web app

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.

Research direction

Start by tracing the web app workflow for the second build phase and how an Ansible failure is represented after the VPN is not configured. Reproduce the listed sequence, then determine where the UI permits only Abort and Destroy. Done means a failed second phase can be retried from the UI without destroying the environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, python
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.