[ENH] Allow to retry 2nd build_lab phase in case VPN connection was not configured or ansible failed.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- ansible, python
- Domain
- devops, infrastructure
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.
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
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 418
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 requestOpen
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 3/5 1-2 days Newbie friendliness 35/100
splunk/attack_range#1367 ·
-
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
conda-forge/conda-build-feedstock#289 · 1 comment · 1 reaction ·
-
`pulptest` no longer works in 4.0.0: `ImportError: Start directory is not importable: 'pulp/tests'`Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
remove reddit feedsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TomCasavant/ohio-sites#224 ·