Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Deployment Plan (Alibaba SMS Integration)

This document explains the deployment plan for the release of the Alibaba SMS integration project to the production environment.

Pre-Deployment Steps

  • Add new environment variable for build process on AWS SSM with name hh_server_build1 (see Appendix A for full URL) or ask the Infrastructure Team to add the environment from Terraform
  • Add new environment variable for Kubernetes server on ConfigMaps

The new environment credentials:

ALIBABA_ACCESS_KEY_ID: <set in AWS SSM>
ALIBABA_ACCESS_KEY_SECRET: <set in AWS SSM>

Real credentials must be set in AWS SSM. Do not commit AccessKey pairs to docs. If the previously committed values are still active, rotate them in the Alibaba Cloud console.

Deployment Steps

  • Merge the PR: https://github.com/hungryhub-team/hh-server/pull/5442
  • Wait for the deployment process to succeed
  • Monitor deployment logs for any errors

Post-Deployment Steps

  • Update SMS Provider on Admin Settings to be alibaba (this is an Alibaba SMS integration)
  • Test sending SMS using the alibaba provider
  • Verify SMS delivery to test phone numbers

Rollback Steps

  • If deployment fails: Revert the PR and redeploy the previous version
  • If SMS fails: Rollback to previous SMS provider configuration in Admin Settings

Prerequisites

  • AWS SSM access for adding environment variables
  • Kubernetes cluster access for ConfigMap updates
  • Admin access to HungryHub Admin Settings
  • Test phone numbers for SMS verification

Appendix A

Full AWS SSM URL: https://ap-southeast-1.console.aws.amazon.com/systems-manager/parameters/