Skip to content

Commit f71be15

Browse files
committed
feat: use stack outputs as env vars for UI build command
Instead of using stack-output which is problematic when you have multiple environments/stages.
1 parent b1268f2 commit f71be15

8 files changed

Lines changed: 465 additions & 264 deletions

File tree

.env

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
SERVERLESS_SERVICE_SUFFIX=-brett
2+
ALARMS_NOTIFICATION_EMAIL=brett.j.andrews@gmail.com

.github/workflows/on-push-to-master.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ jobs:
3737

3838
- name: Package
3939
# TODO: Ideally, we'd package up the prod version, deploy that to stage, then deploy the same packge to prod
40-
run: npm run package:prod
40+
run: npm run package:prod && npm run zip-release
4141

4242
- name: Release
4343
run: npx semantic-release

example.env.development

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
1-
SERVERLESS_SERVICE_SUFFIX=
1+
SERVERLESS_SERVICE_SUFFIX=-myname
22
ALARMS_NOTIFICATION_EMAIL=alert@example.com

0 commit comments

Comments
 (0)