Deploy named local DB sync instances#7
Conversation
findolor
changed the title
findolor
force-pushed
the
feature/deployment-id-deploy-workflow
branch
from
2eb7c17 to
65901bd
Compare
findolor
force-pushed
the
feature/deployment-id-runner
branch
from
bca4841 to
4698d75
Compare
|
Warning Review limit reached
More reviews will be available in 18 minutes and 8 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
findolor
force-pushed
the
feature/deployment-id-deploy-workflow
branch
from
65901bd to
8d192bc
Compare
findolor
force-pushed
the
feature/deployment-id-deploy-workflow
branch
from
8d192bc to
eff0acb
Compare
findolor
force-pushed
the
feature/deployment-id-runner
branch
from
4698d75 to
8698a0c
Compare
findolor
changed the base branch from
feature/deployment-id-runner
to
graphite-base/7
findolor
force-pushed
the
feature/deployment-id-deploy-workflow
branch
from
eff0acb to
6d7400e
Compare
## Depends on - #7 ## Motivation Named deployments need basic operations after they are created: reviewers and operators should be able to see what is running, and old deployment instances should be easy to sunset after the web application has moved to a new manifest. ## Solution - add a manual `List Deployments` workflow that reports deployment ID, timer status, service status, settings URL, service start time, next timer run, and work directory size - add a manual `Sunset Deployment` workflow that stops and disables one named deployment - keep deployment env, binary, and work state by default for rollback - add an explicit `delete_state` option for removing a deployment's host-side state - document deployment IDs, side-by-side operation, listing, and sunset behavior in `README.md` ## Checks By submitting this for review, I am confirming I have done the following: - [x] made this PR as small as possible - [ ] unit-tested any new functionality - [x] linked any relevant issues or PRs - [ ] included screenshots (if this involves a front-end change) Validated locally with: - YAML parse for `.github/workflows/deploy.yaml`, `.github/workflows/list-deployments.yaml`, and `.github/workflows/sunset-deployment.yaml` - `bash -n nixos/local-db-remote-run.sh` - `nix eval '.#nixosConfigurations.local-db-remote.config.systemd.timers."local-db-sync@".timerConfig.Unit'`
3 participants
Depends on
Motivation
Once the host has deployment-id based systemd units, the deployment workflow needs to target one named deployment without stopping or replacing unrelated sync processes.
Solution
deployment_idworkflow inputlocal-db-sync@<deployment_id>.timerandlocal-db-sync@<deployment_id>.serviceChecks
By submitting this for review, I am confirming I have done the following:
Validated locally with:
.github/workflows/deploy.yaml