Commit 73c852a
authored
Fix: Refresh AWS Token During Lambda Java Performance Test (#450)
Problem:
The Lambda Java performance test can take longer than one hour, but the
AWS token is only valid for one hour. If the token expires, the
performance test will fail. Additionally, Terraform will fail to delete
the AWS resources it created. When this happens, subsequent performance
tests are blocked because the AWS resources cannot be manually deleted
(attempts to delete them in the AWS Console result in "Access Denied,"
even with admin permissions).
Fix:
In the performance test workflow, we explicitly renew the AWS token
twice:
Before running the performance tests.
Before tearing down the Terraform-created resources.1 parent 81f92f9 commit 73c852a
1 file changed
+16
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
38 | 38 | | |
39 | 39 | | |
40 | 40 | | |
41 | | - | |
| 41 | + | |
42 | 42 | | |
43 | 43 | | |
44 | 44 | | |
| |||
83 | 83 | | |
84 | 84 | | |
85 | 85 | | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
86 | 93 | | |
87 | 94 | | |
88 | 95 | | |
| |||
131 | 138 | | |
132 | 139 | | |
133 | 140 | | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
134 | 149 | | |
135 | 150 | | |
136 | 151 | | |
| |||
0 commit comments