-
Notifications
You must be signed in to change notification settings - Fork 6
prod automation POC #336
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
base: 2025-05-01-yaml-config
Are you sure you want to change the base?
prod automation POC #336
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Motivation
This is a POC for prod automation for rain solver on digital ocean app platform, this is done through creating specific workflows for each prod action.
Solution
deploymentsfolder that hosts configuration and DigitalOcean app platform specs for the deployment, each sub folder will contain:specs.yaml: Digitalocean App Platform specsconfig.yaml: Rain solver configuration yamlid.txt: This is autogenerated upon deployment of this configuration and keep the deployment id for later actions such as restart, rebuild, update and upgradeHere are the list of workflows that each perform an specific task:
deploy: Deploys a new worker from the specified workflow input options, upon successful deployment, the id will be stored in its folder for later useupgrade: Upgrade all the live prod deployments to latest upstream changes that are pushed on to docker hubupdate: Updates the chosen worker configurations only, without upgrading to latest upstream changesrebuild: Rebuilds the chosen worker from the source (in out case from docker hub)restart: Executes soft reset for the workerChecks
By submitting this for review, I'm confirming I've done the following: