funktor 0.7.19 → 0.7.22
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +2 -2
- data/funktor-testapp/funktor_config/funktor.yml +4 -4
- data/funktor-testapp/funktor_config/resources/cloudwatch_dashboard.yml +324 -220
- data/lib/funktor/cli/templates/funktor_config/resources/cloudwatch_dashboard.yml +229 -146
- data/lib/funktor/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 7520afb50696ff87dea49311326fa2fcb9854c0ba0fd0e25606020853d4689f9
|
|
4
|
+
data.tar.gz: d8f6d65f0a4b6043877b6a9c3eca935bf5ce4175def15325a65126f2bf924512
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f589c07aa5dc31024832ea9ea8a19443e17e617fec6f2be326368b9de613d368e8bd49e9cfdab96df276e30cabe789e55e60e0c057b9bc6570732ed6cd5b1e1d
|
|
7
|
+
data.tar.gz: 85598ac421868b79fbd5f5869db78e4a4369cf0a7a8d0f4c36e51915bb27849665db340fb4512658b51daeec20f1246a6dbf483feea920ab9245ba34395b59c2
|
data/Gemfile.lock
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
funktor (0.7.
|
|
4
|
+
funktor (0.7.22)
|
|
5
5
|
activesupport
|
|
6
6
|
aws-sdk-dynamodb (~> 1.62)
|
|
7
7
|
aws-sdk-sqs (~> 1.37)
|
|
@@ -22,7 +22,7 @@ GEM
|
|
|
22
22
|
addressable (2.8.0)
|
|
23
23
|
public_suffix (>= 2.0.2, < 5.0)
|
|
24
24
|
aws-eventstream (1.2.0)
|
|
25
|
-
aws-partitions (1.
|
|
25
|
+
aws-partitions (1.595.0)
|
|
26
26
|
aws-sdk-core (3.131.1)
|
|
27
27
|
aws-eventstream (~> 1, >= 1.0.2)
|
|
28
28
|
aws-partitions (~> 1, >= 1.525.0)
|
|
@@ -15,7 +15,7 @@ IncomingJobHandler:
|
|
|
15
15
|
# Use memory_size to adjust the reousrces (both memory and CPU) available.
|
|
16
16
|
# For the incoming jobs handler you probably don't need this to be too large,
|
|
17
17
|
# but if you're seeing large delays at this stage it might help to bump it up.
|
|
18
|
-
memorySize:
|
|
18
|
+
memorySize: 128
|
|
19
19
|
batchSize: 1
|
|
20
20
|
maximumBatchingWindow: 0
|
|
21
21
|
visibilityTimeout: 1800
|
|
@@ -38,7 +38,7 @@ JobActivator:
|
|
|
38
38
|
# Use memory_size to adjust the reousrces (both memory and CPU) available.
|
|
39
39
|
# For the job activator you probably don't need this to be too large,
|
|
40
40
|
# but if you're seeing large delays at this stage it might help to bump it up.
|
|
41
|
-
memorySize:
|
|
41
|
+
memorySize: 128
|
|
42
42
|
batchSize: 1
|
|
43
43
|
maximumBatchingWindow: 0
|
|
44
44
|
visibilityTimeout: 1800
|
|
@@ -64,7 +64,7 @@ DefaultQueueHandler:
|
|
|
64
64
|
# For the active jobs handler you'll want this to be at least as large as the memory
|
|
65
65
|
# required to actually do your jobs. You can choose an even higher number to increase
|
|
66
66
|
# the available CPU to make the jobs run faster.
|
|
67
|
-
memorySize:
|
|
67
|
+
memorySize: 128
|
|
68
68
|
batchSize: 1
|
|
69
69
|
maximumBatchingWindow: 0
|
|
70
70
|
visibilityTimeout: 1800
|
|
@@ -88,7 +88,7 @@ LowConcurrencyQueueHandler:
|
|
|
88
88
|
# For the active jobs handler you'll want this to be at least as large as the memory
|
|
89
89
|
# required to actually do your jobs. You can choose an even higher number to increase
|
|
90
90
|
# the available CPU to make the jobs run faster.
|
|
91
|
-
memorySize:
|
|
91
|
+
memorySize: 128
|
|
92
92
|
batchSize: 1
|
|
93
93
|
maximumBatchingWindow: 0
|
|
94
94
|
visibilityTimeout: 1800
|