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
Fixes#567
## What was changed
- When executing short-lived transactional commands (e.g. `start`,
`list` etc, as opposed to the long-running `server start-dev` process)
report errors/warnings as unstructured plain text instead of structured
logging-formatted messages.
- The logger is now used only by the server and SDK
## Why?
CLIs should report errors/warnings by printing to stderr. They should
not use structured logging messages for this.
## How was this tested
- New in-codebase tests
- Manually.
f.Var(&v.LogLevel, "log-level", "Log level. Default is \"info\" for most commands and \"warn\" for \"server start-dev\". Accepted values: debug, info, warn, error, never.")
f.Var(&v.LogLevel, "log-level", "Log level. Default is \"never\" for most commands and \"warn\" for \"server start-dev\". Accepted values: debug, info, warn, error, never.")
s.Command.Flags().StringArrayVar(&s.SqlitePragma, "sqlite-pragma", nil, "SQLite pragma statements in \"PRAGMA=VALUE\" format.")
2119
2119
s.Command.Flags().StringArrayVar(&s.DynamicConfigValue, "dynamic-config-value", nil, "Dynamic configuration value using `KEY=VALUE` pairs. Keys must be identifiers, and values must be JSON values. For example: `YourKey=\"YourString\"` Can be passed multiple times.")
2120
-
s.Command.Flags().BoolVar(&s.LogConfig, "log-config", false, "Log the server config to stderr.")
2120
+
s.Command.Flags().BoolVar(&s.LogConfig, "log-config", false, "Print the server config to stderr.")
2121
2121
s.Command.Flags().StringArrayVar(&s.SearchAttribute, "search-attribute", nil, "Search attributes to register using `KEY=VALUE` pairs. Keys must be identifiers, and values must be the search attribute type, which is one of the following: Text, Keyword, Int, Double, Bool, Datetime, KeywordList.")
0 commit comments