You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the CLI module should basically house the bare minimum level of "standalone app" functionality. There's some stuff in there that might be reusable by another application (for example, we actually import parts of the disease CLI in therapy because it's an easy way to run the updating routines). Maybe we could move some of that up to the etl module or something.
Since the CLI is supposed to be a "standalone app", this could also give us some leeway to set more humane logging parameters there. Currently, DynamoDB produces around 15 lines of logs every second. This might be slowing us down, and also makes actually using the logs kind of difficult since 99.9% of the time the problem is not with some arcane botocore connection (and if it was, I'd never be able to figure it out anyway...). It'd be bad form to change the botocore/boto3 logging levels in importable parts of the normalizer, but we could probably do it within the CLI (maybe enable verbose logging with a CLI option?).
The text was updated successfully, but these errors were encountered:
I think the
CLI
module should basically house the bare minimum level of "standalone app" functionality. There's some stuff in there that might be reusable by another application (for example, we actually import parts of the disease CLI in therapy because it's an easy way to run the updating routines). Maybe we could move some of that up to theetl
module or something.Since the CLI is supposed to be a "standalone app", this could also give us some leeway to set more humane logging parameters there. Currently, DynamoDB produces around 15 lines of logs every second. This might be slowing us down, and also makes actually using the logs kind of difficult since 99.9% of the time the problem is not with some arcane botocore connection (and if it was, I'd never be able to figure it out anyway...). It'd be bad form to change the botocore/boto3 logging levels in importable parts of the normalizer, but we could probably do it within the CLI (maybe enable verbose logging with a CLI option?).
The text was updated successfully, but these errors were encountered: