Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_pipe
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:AP S22-6 (May)
-
Team:Alert Production
-
Urgent?:No
Description
While investigating why the solution to DM-34254 only needs config overrides in the root ApPipe pipeline, I discovered that the hack I'd introduced in DM-31063 blocks its own config settings, not the obs package config's. This is not what we want for cleaning up the AP pipeline configuration.
Find an improved version of the hack that actually resets the pipeline's config. Preliminary experiments have gotten good results with Config.loadFromString and Config.saveToString, but I have not yet tested how this works with configs that may require imports or otherwise alter nested configs.
Hi John Parejko, since this issue is relevant to both
DM-31063andDM-34254, would you be willing to review it? It's 70 lines total.