Skip to content

feat: allow to pass mailprovider as a workflow input #2124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
flea89 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: allow to pass mailprovider as a workflow input #2124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion .github/workflows/cron-storage-limits.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,13 @@ on:
# Including 'workflow_dispatch' here allows the job to be triggered manually,
# as well as on the schedule.
workflow_dispatch:
inputs:
email_provider:
type: choice
description: The mail provider used to send emails to users. Use 'dummy' if you want only to log emails to the console. If not specified the default mail provider is used in prod and the dummy one is used in staging.
options:
- mailchimp
- dummy

jobs:
send-notifications:
Expand Down Expand Up @@ -42,6 +49,6 @@ jobs:
PROD_PG_REST_URL: ${{ secrets.PROD_PG_REST_URL }}
STAGING_PG_REST_URL: ${{ secrets.STAGING_PG_REST_URL }}
MAILCHIMP_API_KEY: ${{ secrets.MAILCHIMP_API_KEY }}
EMAIL_PROVIDER: ${{ (matrix.env == 'staging' && 'dummy') || '' }} # use dummy provider in staging, while using the default provider in prod.
EMAIL_PROVIDER: ${{ github.event.inputs.env || ((matrix.env == 'staging' && 'dummy') || '') }} # use dummy provider in staging, while using the default provider in prod.
run: npm run start:storage -w packages/cron