[FR]: 'configure' should support logging, indicate progress #428
Comments
gregmagolan
pushed a commit
that referenced
this issue
Sep 22, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 4, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 4, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 4, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 7, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 7, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 7, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
jbedard
added a commit
that referenced
this issue
Oct 9, 2023
Moving the gazelle logging util methods to a common util for all of the cli (cli/core/pkg/logger/logger.go). For now this util is the basic go `log` package, if we continue using this util for logging then we can replace the underlying log library with anything in the future. For now there are 2 undocumented env vars to configure logging level + output file. The log file + level is auto configured when used within `bazel test` which has been used by the gazelle tests for quite some time. Ref: #428 #480 #290 #26 GitOrigin-RevId: dd5b7949117ec4298671945d7d0df1ba288b9d8b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the current behavior?
Gazelle is configured to log level WARN and can't be changed:
aspect-cli/gazelle/js/log.go
Line 16 in e95892c
Describe the feature
Ability to set a log level or verbose flag for
aspect configure.The text was updated successfully, but these errors were encountered: