-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add scheduled service #15761
Add scheduled service #15761
Conversation
21da7b0
to
c64325e
Compare
container_name: airbyte-cron | ||
restart: unless-stopped | ||
environment: | ||
- DB=postgresql |
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.
This is not need now but it will be needed in the future for sure. It is better to put it now.
c64325e
to
22bc9a7
Compare
public class MicronautCronRunner { | ||
|
||
@Inject | ||
Temporal temporal; |
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.
If this is just to ensure that the bean gets created, you could also do this through an ApplicationListener or by configuring Micronaut to do eager initialization of Singletons.
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.
Done
I'm probably missing the helm chart in this PR. |
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.
* Add logger scheduled service * Use eager bean initialization
Hi just want to ask @benmoriceau why there is cron deployment. but in the helm charts there isnt
This caused this issue #16698 |
What
This is adding a new app in docker and kube. This app is a micronaut server which allow to have Bean being inject into it. The goal of those bean is to run scheduled activities. The example service is not doing anything on purpose and should be consider as a template.
It has been manually tested on docker using a log.