-
Notifications
You must be signed in to change notification settings - Fork 322
Development
: Add Helios push based lifecycle monitoring with manual DB migration status events
#10873
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
Conversation
Development
: Add Helios status updates library
Development
: Add Helios status updates libraryDevelopment
: Add Helios status updates
This comment was marked as outdated.
This comment was marked as outdated.
c14d36a
This comment was marked as outdated.
This comment was marked as outdated.
Thank you everybody for testing the PR 🙏🏻
I have refactored the library and removed the okhttp3 dependency. Now we are using spring boot's Tested on TS 1,2,3,4,5,6 👍🏻 |
End-to-End (E2E) Test Results Summary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reapprove, tested on Helios, mentioned states observed 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checklist
General
Motivation and Context
Helios currently pulls each environment’s status; this library flips that to a push model:
STARTING_UP
,RUNNING
heart-beats,SHUTTING_DOWN
, andFAILED
.DB_MIGRATION_STARTED
DB_MIGRATION_FINISHED
DB_MIGRATION_FAILED
Description
Added dependency
de.tum.cit.aet:helios-status-spring-starter
(~22 KB)New
helios.status.*
YAML block (see example below).Runtime behaviour
BootLifecycleListener
inside the starter pushes Spring lifecycle events;HeartbeatScheduler
sendsRUNNING
every 30s.DB migration integration
Optional<HeliosClient>
intoDatabaseMigration
andLiquibaseConfiguration
to call:Example
application.yml
(The YAML is set and populated to the nodes in the deployment)/api/environments/status
. secret-key = repo-specific token generated in the Helios UI. Add a second entry if you also want to push to staging, etc.Steps for Testing
Prerequisites:
Steps
Shutting down
,Migrating DB
,Migration finished
,Running
)helios
Screenshots
Screen.Recording.2025-05-19.at.22.47.25.mov
Summary by CodeRabbit
Summary by CodeRabbit
New Features
Chores