You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deep-dive-into-hyperexecute-yaml.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -643,7 +643,7 @@ globalPre:
643
643
runson: win
644
644
cache: true
645
645
```
646
-
646
+
<!--
647
647
:::info
648
648
You can also use `beforeAll` as an alias for the `globalPre` command:
649
649
@@ -655,7 +655,7 @@ beforeAll:
655
655
runson: win
656
656
cache: true
657
657
```
658
-
:::
658
+
:::-->
659
659
660
660
#### Parameters
661
661
| Parameter | Type | Description |
@@ -697,7 +697,7 @@ globalPost:
697
697
runson: linux
698
698
```
699
699
700
-
:::info
700
+
<!-- :::info
701
701
You can also use `afterAll` as an alias for the `globalPost` command:
702
702
703
703
```yaml
@@ -707,7 +707,7 @@ afterAll:
707
707
mode: local
708
708
runson: linux
709
709
```
710
-
:::
710
+
:::-->
711
711
712
712
#### Parameters
713
713
| Parameter | Type | Description |
@@ -1389,10 +1389,10 @@ if your test loads jquery static library multiple times and for some reason it i
1389
1389
1390
1390
> **Note**: These cached resources are not yet shared across VMs. So, each VM has its own copy of cache.
1391
1391
1392
-
<!--
1393
1392
***
1394
1393
1395
-
### `afterAll`
1394
+
### `afterAll`
1395
+
> This flag is deprecated, instead use [`globalPost`](/support/docs/deep-dive-into-hyperexecute-yaml/#globalpost)
1396
1396
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.
1397
1397
```yaml
1398
1398
afterAll:
@@ -1403,10 +1403,12 @@ afterAll:
1403
1403
1404
1404
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 :
1405
1405
- 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
+
***
1407
1409
1408
-
<!-- ***
1409
1410
## `beforeAll`
1411
+
> This flag is deprecated, instead use [`globalPre`](/support/docs/deep-dive-into-hyperexecute-yaml/#globalpre)
1410
1412
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.
1411
1413
```yaml
1412
1414
beforeAll:
@@ -1416,7 +1418,7 @@ beforeAll:
1416
1418
commands:
1417
1419
pip install -r requirements.txt
1418
1420
```
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.
0 commit comments