forked from mendersoftware/deployments
-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.yaml
151 lines (124 loc) · 4.95 KB
/
config.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
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
# API server listen address
# Defauls to: ":8080" which will listen on all avalable interfaces.
# Overwrite with environment variable: DEPLOYMENTS_LISTEN
listen: :8080
# HTTP Server middleware environment
# Available values:
# dev - development environment
# prod - production environment
# Defaults to: prod
# Overwrite with environment variable: DEPLOYMENTS_MIDDLEWARE
# middleware: dev
# HTTPS configuration
# To enable listening using HTTPS protocol please uncomment and configure following section.
# All fields in https section are required if any set.
# Defaults to: unset
# Overwrite with environment variables:
# - DEPLOYMENTS_HTTPS_CERTIFICATE
# - DEPLOYMENTS_HTTPS_KEY
# https:
# certificate: /path/to/certificate
# key: /path/to/private_key
# Mongodb connection string
# Defaults to: "mongo-deployments"
# Overwrite with environment variable: DEPLOYMENTS_MONGO_URL
mongo-url: mongo-deployments
# Enable SSL for mongo connections
# Defaults to: false
# Overwrite with environment variable: DEPLOYMENTS_MONGO_SSL
# mongo_ssl: false
# SkipVerify controls whether a mongo client verifies the
# server's certificate chain and host name.
# If InsecureSkipVerify is true, accepts any certificate
# presented by the server and any host name in that certificate.
# Defaults to: false
# Overwrite with environment variable: DEPLOYMENTS_MONGO_SSL_SKIPVERIFY
# mongo_ssl_skipverify: false
# Mongodb username
# Overwrites username set in connection string.
# Defaults to: none
# Overwrite with environment variable: DEPLOYMENTS_MONGO_USERNAME
# mongo_username: user
# Mongodb password
# Overwrites password set in connection string.
# Defaults to: none
# Overwrite with environment variable: DEPLOYMENTS_MONGO_PASSWORD
# mongo_password: secret
# Inventory service address
# Defaults to: http://mender-inventory:8080
# Env key: DEPLOYMENTS_MENDER_GATEWAY
mender-gateway: "http://mender-inventory:8080"
# AWS configuration section
aws:
# AWS region for minio shoud be "us-east-1"
# Defaults to: us-east-1
# Overwrite with environment variable: DEPLOYMENTS_AWS_REGION
region: us-east-1
# S3 bucket where the uploaded images will be stored and served from.
# Bucket is required to be created before running the service.
# Bucket should allow PUT/GET methods using CORS, example CORS conifg:
# <CORSConfiguration>
# <CORSRule>
# <AllowedOrigin>*</AllowedOrigin>
# <AllowedMethod>PUT</AllowedMethod>
# <AllowedMethod>GET</AllowedMethod>
# <MaxAgeSeconds>3000</MaxAgeSeconds>
# <AllowedHeader>*</AllowedHeader>
# </CORSRule>
# </CORSConfiguration>
# Defaults to: "mender-artifact-storage"
# Overwrite with environment variable: DEPLOYMENTS_AWS_BUCKET
bucket: mender-artifact-storage
# S3 URI
# Defaults to: none (s3.amazonaws.com)
# Overwrite with environment variable: DEPLOYMENTS_AWS_URI
# uri: example.com
# Artifact Tagging
# Defaults to: false
#
# Set to 'true' if you want to tag artifacts on S3 with tenant_id:<tenant_id>
# Note that this does not work on minio, and actually overwrites artifacts to an XML file
#
# tag_artifact: false
#
# Authentication credentials for AWS.
# AWS role requires READ/WRITE permissions for configured S3 bucket.
#
# AWS credentials can be provided with described below methods (checked in sequence):
#
# Environment variables:
# AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
# If you're working with temporary security credentials,
# you can also keep the session token in AWS_SESSION_TOKEN.
#
# If you're testing with a fake s3 environment, you can specify the uri endpoint with: DEPLOYMENTS_AWS_URI
#
# Credentials File:
# Instead of keeping credentials in environment variables,
# you can put credentials into a single file that's located in: ~/.aws/credentials
# An important point is that the default location for the credentials file is a user directory.
#
# The format for the credentials is the same for all the SDKs and the AWS CLI:
#
# [default]
# aws_access_key_id = ACCESS_KEY
# aws_secret_access_key = SECRET_KEY
# aws_session_token = TOKEN
#
# The aws_session_token value is needed only if you're including temporary security credentials in the file.
#
# Alternatively they can be provided directly using "auth" section.
#
# Token is optional, it is needed if working with temporaty credentials.
#
# In case when none of the credential retrieving methods are set, service will default to retrieving authentication
# credentials locally from AWS IAM which is prefered method then running the service in EC2
#
# Overwrite with environment variables:
# - DEPLOYMENTS_AWS_AUTH_KEY
# - DEPLOYMENTS_AWS_AUTH_SECRET
# - DEPLOYMENTS_AWS_AUTH_TOKEN
# auth:
# key: ACCESS_KEY
# secret: SECRET_KEY
# token: TOKEN