-
Notifications
You must be signed in to change notification settings - Fork 3
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 more info to TaskStatus
for notifications
#423
Labels
Comments
I would also add:
|
Great, will add |
++ There is difference in Skipped status between TaskStatus and RunStatus. Missing isWarning |
Also missing notification warning/errors ... I am thinking is there a difference between classes and why not have have the same classes for both |
yruslan
added a commit
that referenced
this issue
Jun 17, 2024
yruslan
added a commit
that referenced
this issue
Jun 17, 2024
yruslan
added a commit
that referenced
this issue
Jun 17, 2024
yruslan
added a commit
that referenced
this issue
Jun 17, 2024
yruslan
added a commit
that referenced
this issue
Jun 18, 2024
yruslan
added a commit
that referenced
this issue
Jun 18, 2024
yruslan
added a commit
that referenced
this issue
Jun 20, 2024
yruslan
added a commit
that referenced
this issue
Jun 20, 2024
yruslan
added a commit
that referenced
this issue
Jun 20, 2024
yruslan
added a commit
that referenced
this issue
Jun 20, 2024
yruslan
added a commit
that referenced
this issue
Jun 20, 2024
yruslan
added a commit
that referenced
this issue
Jun 20, 2024
Closed by #428 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
There are some bits of information that is present in the pipeline state, but missing for notification targets, including:
val isFailure: Boolean
Feature
Add the missing information to the
TaskStatus
model objects so that notification targets other then email have access to the same info as email notificationExample
--
Proposed Solution
As an additional suggestion - add access to pipeline state via
PipelineState
trait if client includespramen-core
as a dependency, not justpramen-api
The text was updated successfully, but these errors were encountered: