Skip to content
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.

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

Production deploy setup #37

Merged
merged 7 commits into from
Oct 5, 2023
Merged

Production deploy setup #37

merged 7 commits into from
Oct 5, 2023

Conversation

zwolf
Copy link
Member

@zwolf zwolf commented Oct 4, 2023

  • Nearly everything Eras needs to deploy to production. Deploys via production-release tag as usual. Includes startup/liveness probes and adds them for staging.
  • Took a wild guess about resource utilization--staging is minuscule but prod is gonna be getting the kinesis firehose.
  • Database migrates on deploy via a job, if it's unsuccessful the deploy will halt.
  • Removes tag deploy for lambda, these are both now manual deploys (workflow dispatches) only and environment specific. Both prod and staging use the same function, which is deployed to two different lambdas with different endpoints.

The prod TS database still needs to be created pending confirmation of tier. New lambda has been created and needs to be deployed and connected to the prod kinesis trigger.

@zwolf
Copy link
Member Author

zwolf commented Oct 4, 2023

I created the database and also the production credentials file with db & kinesis creds in it. I stored the new production master key in a kubernetes secret. Also added the production db migration job, which will run on deploy after the image build/push and before the k8s deploy.

@zwolf zwolf requested a review from yuenmichelle1 October 4, 2023 18:33
@zwolf zwolf merged commit 39b396e into main Oct 5, 2023
3 checks passed
@zwolf zwolf deleted the production-deploy branch October 5, 2023 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants