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
# this file is defined in validator/src/main/resources/validations
25
+
validation_config="statsd-metric-validation.yml"
26
+
27
+
data_emitter_image="alpine/socat:latest"
28
+
```
29
+
16
30
### 1.2 add an ec2 testing suite
17
31
18
32
specify below config in the tfvars file
@@ -21,15 +35,24 @@ specify below config in the tfvars file
21
35
3. validation_config, please put a new validation config file under `validator/src/main/resources/validations` folder and specify the filename in the tfvars file.
22
36
4.[optional] sample_app_callable, by default it's true, only set it to false when you don't have a web application sample app image
23
37
5.[optional] data_emitter_image, if you have a sample app then set its image name here
24
-
6.[optional] package_s3_bucket, if you have an aoc rpm/deb/msi built with the new component, and uploaded it to s3, then set its s3 bucket name here.
25
38
7.[optional] aoc_version, if you have an aoc rpm/dev/msi you just built with the new component, then set it as its tag name.
26
39
27
-
please note the rpm/dev/msi s3 object path should be
# this file is defined in validator/src/main/resources/validations
74
+
validation_config="statsd-metric-validation.yml"
75
+
76
+
data_emitter_image="alpine/socat:latest"
77
+
```
78
+
44
79
### 1.4 how to write the configurations?
45
80
81
+
You are able to use placeholders in your configuration files, the testing framework will replace the placeholders with its runtime value when you run the testing suite.
82
+
46
83
#### 1.4.1 otconfig
47
84
48
85
Below are the placeholders you can use in the otconfig
@@ -269,6 +306,10 @@ Below are the placeholders you can use in the expected data pattern.
0 commit comments