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: README.md
+20-13Lines changed: 20 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -223,26 +223,33 @@ set --rate-limit-pr-creations with appropriate value. More example below
223
223
224
224
##### Default case:
225
225
226
+
By default, this feature is disabled. This will be enabled when argument ``--rate-limit-pr-creations`` will be passed
227
+
with
228
+
appropriate value.
229
+
226
230
```
227
231
example usage: dockerfile-image-update all image-tag-store-repo-falcon //disabled
228
-
example usage: dockerfile-image-update --rate-limit-pr-creations 500 all image-tag-store-repo-falcon //enabled
229
232
```
230
-
By default, this feature is disabled. This will be enabled when argument ``--useratelimiting`` will be passed appropriate value
231
-
Above example will throttle the number of PRs cut based on default values as mentioned above i.e.,
232
-
maximum 500 PRs could be sent within a period of 1 hour . To distribute the load uniformly and avoid sudden spikes,
233
-
at max only 8(500/60) PRs could be sent in every 1 min. The process will go in waiting state until next PR could be sent.
234
233
235
234
##### Configuring the rate limit:
236
235
236
+
Below are some examples that will throttle the number of PRs cut based on values passed to the
237
+
argument ``--rate-limit-pr-creations``
238
+
The argument value should be in format ``<positive_integer>-<ISO-8601_formatted_time>``.
239
+
For example ``--rate-limit-pr-creations 60-PT1H`` would mean the tool will cut 60 PRs every hour and the rate of adding
240
+
a new PR will be (PT1H/60) i.e. one minute.
241
+
This will distribute the load uniformly and avoid sudden spikes, The process will go in waiting state until next PR
242
+
could be sent.
243
+
244
+
Below are some more examples:
245
+
237
246
```
238
-
example usage:
239
-
dockerfile-image-update --rate-limit-pr-creations 500 all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per hour
240
-
dockerfile-image-update --rate-limit-pr-creations 500-per-s all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per second
241
-
dockerfile-image-update --rate-limit-pr-creations 500-per-60s all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per 60 second
242
-
dockerfile-image-update --rate-limit-pr-creations 500-per-m all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per minute
243
-
dockerfile-image-update --rate-limit-pr-creations 500-per-1h all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per hour
244
-
dockerfile-image-update --rate-limit-pr-creations 500-per-h all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per hour
245
-
dockerfile-image-update --rate-limit-pr-creations 50perhour all image-tag-store-repo-falcon //DFIU will not impose any rate limiting as argument value is not valid
247
+
Usage:
248
+
dockerfile-image-update --rate-limit-pr-creations 60-PT1H all image-tag-store-repo-falcon //DFIU can send up to 60 PRs per hour.
249
+
dockerfile-image-update --rate-limit-pr-creations 500-PT1H all image-tag-store-repo-falcon //DFIU can send up to 500 PRs per hour.
250
+
dockerfile-image-update --rate-limit-pr-creations 86400-PT24H all image-tag-store-repo-falcon //DFIU can send up to 1 PRs per second.
251
+
dockerfile-image-update --rate-limit-pr-creations 1-PT1S all image-tag-store-repo-falcon //Same as above. DFIU can send up to 1 PRs per second.
252
+
dockerfile-image-update --rate-limit-pr-creations 5000 all image-tag-store-repo-falcon //rate limiting will be disabled because argument is not in correct format.
0 commit comments