-
-
Notifications
You must be signed in to change notification settings - Fork 2
/
nitric.test.yaml
80 lines (75 loc) · 2.93 KB
/
nitric.test.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
# The nitric provider to use
provider: nitric/[email protected]
# The target aws region to deploy to
# See available regions:
# https://docs.aws.amazon.com/general/latest/gr/lambda-service.html
region:
# Optional Configuration Below
batch-compute-env:
min-cpus: 0
max-cpus: 4
instance-types:
- g5 # Or use another GPU supported instance
- optimal
# The timezone that deployed schedules will run with
# Format is in tz identifiers:
# https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
# schedule-timezone: Australia/Sydney # Available since v0.27.0
# Import existing AWS Resources
# Currently only secrets are supported
# Available since v0.28.0
# import:
# # A name ARN map of secrets, where the name matches the nitric name of the secret you would like to import
# secrets: # Available since v0.28.0
# # In typescript this would import the provided secret reference for a secret declared as
# # const mySecret = secret('my-secret');
# my-secret: arn:...
# # Apply configuration to nitric APIs
# apis:
# # The nitric name of the API to configure
# my-api:
# # Array of domains to apply to the API
# # The domain or parent domain must have a hosted zone already in Route53
# domains:
# - api.example.com
# # Configure your deployed functions/services
config:
# How functions without a type will be deployed
default:
# configure a sample rate for telemetry (between 0 and 1) e.g. 0.5 is 50%
# telemetry: 0
# configure functions to deploy to AWS lambda
lambda: # Available since v0.26.0
# set the memory in MB
# See lambda configuration docs here:
# https://docs.aws.amazon.com/lambda/latest/dg/configuration-function-common.html#configuration-memory-console
memory: 1024
# set a timeout in seconds
# See lambda timeout values here:
# https://docs.aws.amazon.com/lambda/latest/dg/configuration-function-common.html#configuration-timeout-console
timeout: 900
# set the amount of ephemeral-storage in MB
# For info on ephemeral-storage for AWS Lambda see:
# https://docs.aws.amazon.com/lambda/latest/dg/configuration-ephemeral-storage.html
# Available Since nitric/[email protected]
ephemeral-storage: 10000
# # set a provisioned concurrency value
# # For info on provisioned concurrency for AWS Lambda see:
# # https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html
# provisioned-concurrency: 0
# # Configure VPCs that the lambda can access
# vpc:
# # Array of existing security group ids to apply
# security-group-ids:
# - sg-xxx
# # Array of existing subnet ids to apply
# subnet-ids:
# - subnet-xxx
# # Additional deployment types
# # You can target these types by setting a `type` in your project configuration
# big-service:
# telemetry: 0
# lambda:
# memory: 1024
# timeout: 60
# provisioned-concurrency: 1