Skip to content

Commit 634d2c2

Browse files
hiding afterAll and beforeAll flags
1 parent 5d59270 commit 634d2c2

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

docs/deep-dive-into-hyperexecute-yaml.md

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -643,7 +643,7 @@ globalPre:
643643
runson: win
644644
cache: true
645645
```
646-
646+
<!--
647647
:::info
648648
You can also use `beforeAll` as an alias for the `globalPre` command:
649649

@@ -655,7 +655,7 @@ beforeAll:
655655
runson: win
656656
cache: true
657657
```
658-
:::
658+
::: -->
659659

660660
#### Parameters
661661
| Parameter | Type | Description |
@@ -697,7 +697,7 @@ globalPost:
697697
runson: linux
698698
```
699699

700-
:::info
700+
<!-- :::info
701701
You can also use `afterAll` as an alias for the `globalPost` command:
702702

703703
```yaml
@@ -707,7 +707,7 @@ afterAll:
707707
mode: local
708708
runson: linux
709709
```
710-
:::
710+
::: -->
711711

712712
#### Parameters
713713
| Parameter | Type | Description |
@@ -1389,10 +1389,10 @@ if your test loads jquery static library multiple times and for some reason it i
13891389

13901390
> **Note**: These cached resources are not yet shared across VMs. So, each VM has its own copy of cache.
13911391

1392-
<!--
13931392
***
13941393

1395-
### `afterAll`
1394+
### `afterAll`
1395+
> This flag is deprecated, instead use [`globalPost`](/support/docs/deep-dive-into-hyperexecute-yaml/#globalpost)
13961396
It is used to run commands after the job has finished. Currently only local directive is allowed, means that all the commands would be run on the same host on which HyperExecute CLI was run. Running commands in `afterAll` on HyperExecute VMs(remote commands) is not yet supported. Users will have access to all the artifacts when these commands would be run.
13971397
```yaml
13981398
afterAll:
@@ -1403,10 +1403,12 @@ afterAll:
14031403

14041404
For instance you want to further process the artifacts and create a custom PDF. You can use `afterAll` for this purpose wherein custom commands can be invoked. Other use cases can be in case you :
14051405
- Want to run some commands after the job is finished.
1406-
- Want to run these commands from the same host from which hyperexecute-cli is run. -->
1406+
- Want to run these commands from the same host from which hyperexecute-cli is run.
1407+
1408+
***
14071409

1408-
<!-- ***
14091410
## `beforeAll`
1411+
> This flag is deprecated, instead use [`globalPre`](/support/docs/deep-dive-into-hyperexecute-yaml/#globalpre)
14101412
BeforeAll is used for running pre operations like discovery and payload_update. It can be executed either on local system or on hyperexecute beforeAll VM.
14111413
```yaml
14121414
beforeAll:
@@ -1416,7 +1418,7 @@ beforeAll:
14161418
commands:
14171419
pip install -r requirements.txt
14181420
```
1419-
We can choose to run on local/remote(on HYP Vms) from the location command. Type can be either discovery/update_payload (type of operation to be performed) and commands will have all the commands that needs to be run for that operation. -->
1421+
We can choose to run on local/remote(on HYP Vms) from the location command. Type can be either discovery/update_payload (type of operation to be performed) and commands will have all the commands that needs to be run for that operation.
14201422

14211423
***
14221424

0 commit comments

Comments
 (0)