Step 8 - Deploy to Production
Run the deploy command
You can use the command line to push your integrations to production once you are ready.
Consider using a separate terminal window so you can continue to run your dev server.
npm run deployIf all goes well, you should see something like this
CLI: [INFO]: Deploying to prod
CLI: [INFO]: Successful build
Server: [INFO]: Publishing lambda
Server: [INFO]: Deploying helloWorld, basicWebhook, helloSlack, githubWebhook, githubToSlack
Server: [INFO]: Deploy succeeded
Server: [INFO]: Evaluated all subscribeProps
Server: [INFO]: Skipping subscribe for webhooks that need configuration: githubWebhook
Deploy succeeded! 🚀Verify the deploy worked
In order to verify that the deploy worked, return to your dashboard (opens in a new tab) and switch to your production environment
and you should be able to see all the actions.
Click the GitHub to Slack action
Fill in a value for the channel variable. Now you may be wondering, why do I have to do this again? The answer is that you will often want different values for variables in the production environment than you do for the development environment. Try choosing a different channel than you used in the previous step.
Now go to the webhooks menu and select the GitHub Webhook webhook.
Configure the variables
Now push a commit to the repo you just specified.
Check out the Deliveries tab to see the webhook data.
Received POST at /api/v1/endpoints/f35bc5d9-9726-4b7d-a483-02c0c994b454
Triggering run on action githubToSlack
Success
And check out the Runs tab on the GitHub to Slack action
Running action githubToSlack
Got a workflow run payload
Posted message to Slack
If everything went well, you should see a Slack message in the channel you just configured. The key difference from the previous step is that the action ran in your production environment (i.e. on our servers) and not your local dev server.