Closed ryanluu12345 closed 1 month ago
@bobvawter I've taken an initial look at this and have a high level idea of how to implement this. The current thinking I have here is to:
factory
struct inside of the stage package. The key reason for this is that we can pass in a new config object inside of stage.ProvideFactory
that lets the frontends configure this via a flag.newStage
so that it takes in this value from the factory struct fieldI don't have questions about the above methodology, but I do have open questions about alternatives I'm considering:
Staging
configuration object. Originally I was thinking I could make a new config.go
inside of the internal/staging/stage
package, but after seeing there is already a Staging
package, wondering if I should put it inside of there? The one consideration I have here is that if we do it this way, then we'll need to have stage
's ProvideFactory
reference the sinkprod.StagingConfig
. I also don't like that the flag and its default will be defined in a package not colocated with the newStage
consistency check logic.I'm just about done implementing this. I'd like to present it to the customer this afternoon.
Noted. Thanks! Please let me know when it is ready and I can review the PR.
The default should run less frequently than it currently does. This should also be configurable. The impact here is that if it runs less frequently, alerting analytics will be slower to fire leading to a bigger window for inconsistency.