Skip to content

Trellis-API: Add rollback verification after failed migrations or deployments #289

Closed

Description

@preshotta

Goal

Implement Add rollback verification after failed migrations or deployments for Trellis-API.

Acceptance criteria

  • Cover normal, failure, retry, and authorization paths.
  • Add automated tests or executable verification.
  • Document operational edge cases and recovery/rollback behavior.
  • Preserve existing contracts or include a migration plan.

This is a hard contributor task; prefer a focused vertical slice over a broad rewrite.

Activity

  1. mysteriousskater commented on Oct 18, 2026

    @mysteriousskater

    @mysteriousskater has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi I’ll like to take ownership of this issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @mysteriousskater to this issue.

  2. padenijinfinity-afk commented on Oct 18, 2026

    @padenijinfinity-afk

    @padenijinfinity-afk has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi, I’d like to take this issue. Rollback verification after a failed migration or deployment is the kind of change where a silent failure is worse than an error, so I’d want the verification to be explicit: confirm the system is back in the expected state and fail loudly if it isn’t.

    My plan:

    Read the current flow: Trace how migrations and deployments are run and where rollback is triggered today, so the verification hooks into existing behaviour rather than duplicating it.
    Add verification: After a rollback, check the resulting state against the pre-migration baseline and report any mismatch clearly.
    Tests: Cover a successful rollback, a failed rollback that should be reported, and a failed migration that triggers the verification path.
    Delivery: Follow the repository’s contribution guidelines for branching and commit messages, and run the existing test suite before opening the PR.

    I’ve worked on full-stack and backend-adjacent projects, including REST APIs and payment integrations (Paystack and Stripe), where a failed state change has to be detected and handled rather than ignored. I’m comfortable reading an unfamiliar codebase and its tests before changing anything

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @padenijinfinity-afk to this issue.

  3. rubbathabrahband commented on Oct 18, 2026

    @rubbathabrahband
    Contributor

    @rubbathabrahband has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    maintainerrr assign this to me

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @rubbathabrahband to this issue.

  4. drips-wave commented on Oct 18, 2026

    @drips-wave

    Congratulations, @rubbathabrahband! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @rubbathabrahband: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  5. rubbathabrahband commented on Oct 18, 2026

    @rubbathabrahband
    Contributor

    Resolved in PR #332: implemented RollbackVerificationService with pre- and post-rollback schema invariant, lock, referential integrity, and smoke query verification.

  6. drips-wave commented on Oct 23, 2026

    @drips-wave

    This issue has been completed by @rubbathabrahband as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @rubbathabrahband: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions