utkarsharma2 commented on PR #27481:
URL: https://github.com/apache/airflow/pull/27481#issuecomment-1302886150
Summy of all the approaches that I could think of:
### Approach 1:
In task instance model introduce a new property, `user_updated_state`: Bool
= True/False; default False
#### Will be updated from:
1. From UI
2. Rest API
1. We will have to expose this parameter in Rest API
2. Default value should be true, since if user creates his own view he
have an option to control it.
3. CLI
#### How will we update the UI in case the user has updated the state:
1. Tool Tip?
### Approach 2
Look in the
[[logs](https://github.com/apache/airflow/blob/3aadc44a13d0d100778792691a0341818723c51c/airflow/models/log.py#L27)](https://github.com/apache/airflow/blob/3aadc44a13d0d100778792691a0341818723c51c/airflow/models/log.py#L27).
When rendering the UI we can a look in logs for events like `Confirm` for the
task id, dag id and execution_date
#### Will be updated from:
1. UI
2. REST API
3. CLI
We don’t need to track this, because it should already be taken care of by
Logs.
#### How will we update the UI in case the user has updated the state:
1. Tool Tip?
### Approach 3:
Add a new state to indicate if the user has marked as a success or failure
#### Will be updated from:
1. From UI
2. Rest API
1. We will have to expose this parameter in Rest API
2. Default value should be true, since if user creates his own view he
have an option to control it.
3. CLI
#### How will we update the UI in case the user has updated the state:
1. New color for new task state
Thanks, @feluelle for helping out :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
