Releases: LykkeCity/lykke.dotnettemplates
Releases · LykkeCity/lykke.dotnettemplates
2.0.0
1.1.1
1.1.0
Mandatory features
- Delay of the process termination on startup failure was added. It required for startup failure determination while running in the Kubernetes.. Diff
- Process start/stop monitoring was added. Diff
Changes
- RabbitMq publisher sample in Job was made synchronous by default. Diff
1.0.0
Release notes
1.0.0
Features
New job template's flags
You can use these flags with dotnet new lkejob command. All flags default value is true, it means, that by default all features are enabled. If you want to disable some features, specify respective flags with false value. (ex: -az false -ra false)
- -az|--azurequeuesub - Enables incoming Azure Queue messages processing, using Lykke.JobTriggers package
- -r|--rabbitsub - Enables incoming RabbitMQ messages processing
- -ra|---rabbitpub - Enables outcoming RabbitMQ messages sending
- -t|--timeperiod - Enables periodical work execution, using TimerPeriod class from Lykke.Common package
Job's contract assembly
Lykke.Job.LykkeJob.Contract assembly was added to the solution template. This assembly usable only when your job provides some contract for other jobs and services via messages. Put outgoing messages into this assembly and setup nuget package deployment in Team City. This will simplify integration of your job's clients. If your job hasn't public contract, just leave this assembly empty.
Explicit startup and shutdown process
- StartupManager and ShutdownManager was introduced in job's and service's templates. Use these classes, if your need to manage startup and shutdown processes explicitly. For example, if you need to restore some state, before subscribe to the incoming messages, or run periodical work.
Breaking changes
Removed job template's flags
- -e|--examples - Examples was removed