Details
-
Type:
Improvement
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: ap_association
-
Labels:
-
Story Points:4
-
Epic Link:
-
Team:Alert Production
Description
Currently, the location of the association database is specified by AssociationDBSqliteConfig. This makes it difficult to call AssociationTask as a subtask of, e.g., ApPipeTask: the desired behavior is for the database file to be found in the output repository, even if it's not recognized by the Butler, but the repository is specified separately from the task configuration (in particular, it cannot be defaulted).
It would be helpful if AssociationTask or AssociationDBSqliteTask allowed the database file to be provided as an input argument, so that parent tasks can set it in response to their input arguments.
This issue will be made obsolete by completion of DM-11767.
Given
DM-13672, it may be better to pass the DB information to run instead of the constructor(though, in isolation, the latter approach makes much more sense).
[See discussion onDM-13672about idiomatic task APIs].