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: zero-module.yml
+42-17Lines changed: 42 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ requiredCredentials:
23
23
parameters:
24
24
- field: useExistingAwsProfile
25
25
label: "Use credentials from an existing AWS profile?"
26
+
info: "You can choose either a currently existing profile if you've already configured your AWS CLI, or manually enter a pair of AWS access keys."
26
27
options:
27
28
"yes": "Yes"
28
29
"no": "No"
@@ -36,6 +37,7 @@ parameters:
36
37
matchField: useExistingAwsProfile
37
38
- field: accessKeyId
38
39
label: AWS AccessKeyId
40
+
info: "AWS access is controlled by a pair of keys tied to a user account.\nhttps://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html "
39
41
envVarName: "AWS_ACCESS_KEY_ID"
40
42
conditions:
41
43
- action: KeyMatchCondition
@@ -44,66 +46,80 @@ parameters:
44
46
- field: secretAccessKey
45
47
envVarName: "AWS_SECRET_ACCESS_KEY"
46
48
label: AWS SecretAccessKey
49
+
info: "AWS access is controlled by a pair of keys tied to a user account.\nhttps://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html "
47
50
conditions:
48
51
- action: KeyMatchCondition
49
52
whenValue: "no"
50
53
matchField: useExistingAwsProfile
51
54
- field: githubAccessToken
52
55
label: "Github API Key to setup your repository and optionally CI/CD"
56
+
info: "This API key will let us set up new repositories to check in your code.\nhttps://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token"
53
57
envVarName: GITHUB_ACCESS_TOKEN
54
58
- field: region
55
59
label: Select AWS Region
60
+
info: "This is the region your resources will be created in.\nMost regions have all the same features and functionality, but depending on your product you may need to choose a different region for data sovereignty reasons."
56
61
options:
57
-
"us-west-2": "us-west-2 (Oregon)"
58
-
"us-east-1": "us-east-1 (N. Virginia)"
59
-
"us-east-2": "us-east-2 (Ohio)"
62
+
"us-east-1": "us-east-1 - US East (N. Virginia)"
63
+
"us-east-2": "us-east-2 - US East (Ohio)"
64
+
"us-west-2": "us-west-2 - US West (Oregon)"
65
+
"ca-central-1": "ca-central-1 - Canada (Central)"
66
+
"eu-west-1": "eu-west-1 - Europe (Ireland)"
67
+
"ap-southeast-1": "ap-southeast-1 - Asia Pacific (Singapore)"
60
68
- field: productionHostRoot
61
-
label: Production Root Host Name (e.g. mydomain.com) - this must be the root of the chosen domain, not a subdomain.
69
+
label: Production Root Host Name (e.g. mydomain.com)
70
+
info: "This must be the root of the chosen domain, not a subdomain. You will also be prompted for the subdomains to use for your application."
info: "The subdomain that will point to the static assets of your frontend hosted in Cloudfront."
68
78
default: app.
69
79
fieldValidation:
70
80
type: regex
71
81
value: '^([a-z0-9]+(-[a-z0-9]+)*\.)$'
72
82
errorMessage: Invalid subdomain (cannot contain special chars & must end with a '.')
73
83
- field: productionBackendSubdomain
74
84
label: Production Backend Host Name (e.g. api.)
85
+
info: "The subdomain that will point to the API of your backend running in Kubernetes."
75
86
default: api.
76
87
fieldValidation:
77
88
type: regex
78
89
value: '^([a-z0-9]+(-[a-z0-9]+)*\.)$'
79
90
errorMessage: Invalid subdomain (cannot contain special chars & must end with a '.')
80
91
- field: stagingHostRoot
81
-
label: Staging Root Host Name (e.g. mydomain-staging.com) - this must be the root of the chosen domain, not a subdomain.
92
+
label: Staging Root Host Name (e.g. mydomain-staging.com)
93
+
info: "This must be the root of the chosen domain, not a subdomain. You will also be prompted for the subdomains to use for your application.\nIt's recommended that you use different hostnames for staging and production instead of trying to have staging as a subdomain of your production domain."
info: "The subdomain that will point to the static assets of your frontend hosted in Cloudfront."
88
101
default: app.
89
102
fieldValidation:
90
103
type: regex
91
104
value: '^([a-z0-9]+(-[a-z0-9]+)*\.)$'
92
105
errorMessage: Invalid subdomain (cannot contain special chars & must end with a '.')
93
106
- field: stagingBackendSubdomain
94
107
label: Staging Backend Host Name (e.g. api.)
108
+
info: "The subdomain that will point to the API of your backend running in Kubernetes."
95
109
default: api.
96
110
fieldValidation:
97
111
type: regex
98
112
value: '^([a-z0-9]+(-[a-z0-9]+)*\.)$'
99
113
errorMessage: Invalid subdomain (cannot contain special chars & must end with a '.')
100
114
- field: database
101
-
label: Database engine to use (postgres)
115
+
label: Database engine to use
116
+
info: "This will set up a database for you using RDS.\nIt will be accessible only by your application, credentials will be created automatically."
102
117
options:
103
118
"postgres": "PostgreSQL"
104
119
"mysql": "MySQL"
105
120
- field: cacheStore
106
-
label: "Cache store to use (default: no cache)"
121
+
label: "Cache store to use"
122
+
info: "If necessary for your application, this will set up a cache using AWS ElastiCache."
107
123
options:
108
124
"none": "none"
109
125
"redis": "Redis"
@@ -117,55 +133,64 @@ parameters:
117
133
- field: databaseName
118
134
execute: echo "$projectName"| sed "s/[- ]//g"
119
135
- field: fileUploads
120
-
label: Enable file uploads using S3 and Cloudfront signed URLs? (Will require manual creation of a Cloudfront keypair in AWS)
136
+
label: Enable file uploads using S3 and Cloudfront signed URLs?
137
+
info: "This will allow secure file uploads and downloads through your application.\nIt will require manual creation of a Cloudfront keypair in AWS. See https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-trusted-signers.html"
121
138
default: yes
122
139
options:
123
140
"yes": "Yes"
124
141
"no": "No"
125
142
- field: userAuth
126
-
label: Enable user management using Kratos and authentication using the Oathkeeper access proxy?
143
+
label: Enable user management and auth access proxy?
144
+
info: "This will enable infrastructure and application code that uses Kratos for user management and the Oathkeeper access proxy.\nhttps://ory.sh"
127
145
default: yes
128
146
options:
129
147
"yes": "Yes"
130
148
"no": "No"
131
149
- field: CIVendor
132
-
label: Using either circleCI or github Actions to build / test your repository
150
+
label: Which CI vendor would you like to use?
151
+
info: "Build pipelines will be set up which will deploy your code to your infrastructure whenever PRs are merged to the main branch."
133
152
default: "circleci"
134
153
options:
135
-
"circleci": "CircleCi"
154
+
"circleci": "CircleCI"
136
155
"github-actions": "Github Actions"
137
156
- field: circleciApiKey
138
-
label: "Circle CI API Key to setup your CI/CD for repositories"
157
+
label: "CircleCI API Key"
158
+
info: "This will let us configure your CircleCI account to automatically enable CI for these newly created projects.\nhttps://circleci.com/docs/2.0/managing-api-tokens/"
139
159
envVarName: CIRCLECI_API_KEY
140
160
conditions:
141
161
- action: KeyMatchCondition
142
162
matchField: CIVendor
143
163
whenValue: "circleci"
144
164
- field: billingEnabled
145
-
label: "Provides a subscription example using stripe in backend and frontend repository, this includes the checkout feature so you must have a verified(with bank account setup) Stripe account to use these features"
165
+
label: "Enable billing support?"
166
+
info: "Provides a subscription example using stripe in the backend and frontend repositories."
146
167
options:
147
168
"yes": "Yes"
148
169
"no": "No"
149
170
- field: stagingStripePublicApiKey
150
-
label: "Staging Stripe public api key, used for frontend repository (Recommended: using sandbox key while setting up)"
171
+
label: "Staging Stripe public api key"
172
+
info: "Used for the frontend repository. It's recommended to use a sandbox key while getting set up."
151
173
conditions:
152
174
- action: KeyMatchCondition
153
175
matchField: billingEnabled
154
176
whenValue: "yes"
155
177
- field: stagingStripeSecretApiKey
156
-
label: "Staging Stripe secret api key, used for backend repository (Recommended: using sandbox key while setting up)"
178
+
label: "Staging Stripe secret api key"
179
+
info: "Used for the backend repository. It's recommended to use a sandbox key while getting set up."
157
180
conditions:
158
181
- action: KeyMatchCondition
159
182
matchField: billingEnabled
160
183
whenValue: "yes"
161
184
- field: productionStripePublicApiKey
162
-
label: "Production Stripe public api key, used for frontend repository (Recommended: using sandbox key while setting up)"
185
+
label: "Production Stripe public api key"
186
+
info: "Used for the frontend repository. It's recommended to use a sandbox key while getting set up."
163
187
conditions:
164
188
- action: KeyMatchCondition
165
189
matchField: billingEnabled
166
190
whenValue: "yes"
167
191
- field: productionStripeSecretApiKey
168
-
label: "Production Stripe secret api key, used for backend repository (Recommended: using sandbox key while setting up)"
192
+
label: "Production Stripe secret api key"
193
+
info: "Used for the backend repository. It's recommended to use a sandbox key while getting set up."
0 commit comments