Skip to content
This repository has been archived by the owner on Jul 30, 2020. It is now read-only.

Review logging and default logging config (make sure default level is INFO) #267

Closed
alikins opened this issue May 21, 2019 · 0 comments · Fixed by #273
Closed

Review logging and default logging config (make sure default level is INFO) #267

alikins opened this issue May 21, 2019 · 0 comments · Fixed by #273

Comments

@alikins
Copy link
Contributor

alikins commented May 21, 2019

Bug Report

Review logging and default logging config (make sure default level is INFO)
before 1.0.0.

Cleanup debug logging, etc.

@alikins alikins added this to the Mazer 1.0.0 milestone May 21, 2019
@alikins alikins self-assigned this May 21, 2019
@alikins alikins added status/in-progress and removed status/new Triage required labels May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
Move the impl details of collecting the mazer version info
for `mazer version` to ansible_galaxy.mazer_version so that
other modules can use it (namely, ansible_galaxy.cli.galaxy
for logging info at cli startup)

Fixes ansible#267
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
And 'info' level log the exit code.

For ex:

[2019-05-30 11:17:51,249 28223 I] ansible_galaxy_cli.cli.galaxy run:236 - \
  exe="/home/adrian/venvs/mazer040test/bin/mazer" version=0.5.0 \
  config_file="/home/adrian/.ansible/mazer.yml" \
  collections_path="/home/adrian/.ansible/collections" \
  server=http://localhost:8000 action=install

Fixes ansible#267
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
So a logging config (the default logging config in particular)
can provide a 'basename' arg for
ExpandTildeWatchedFileHandler that will be used relative to
MAZER_HOME.

So:
    $ mkdir /tmp/mazer_home
    $ MAZER_HOME=/tmp/mazer_home mazer install testing.foo

Will use any config in /tmp/mazer_home/, plus by default install
collections to MAZER_HOME/collections, will also now log by
default to MAZER_HOME/mazer.log and MAZER_HOME/mazer-http.log

Fixes ansible#267
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
Move the impl details of collecting the mazer version info
for `mazer version` to ansible_galaxy.mazer_version so that
other modules can use it (namely, ansible_galaxy.cli.galaxy
for logging info at cli startup)

Fixes ansible#267
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
And 'info' level log the exit code.

For ex:

[2019-05-30 11:17:51,249 28223 I] ansible_galaxy_cli.cli.galaxy run:236 - \
  exe="/home/adrian/venvs/mazer040test/bin/mazer" version=0.5.0 \
  config_file="/home/adrian/.ansible/mazer.yml" \
  collections_path="/home/adrian/.ansible/collections" \
  server=http://localhost:8000 action=install

Fixes ansible#267
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit to alikins/mazer that referenced this issue May 30, 2019
alikins added a commit that referenced this issue May 30, 2019
So a logging config (the default logging config in particular)
can provide a 'basename' arg for
ExpandTildeWatchedFileHandler that will be used relative to
MAZER_HOME.

So:
    $ mkdir /tmp/mazer_home
    $ MAZER_HOME=/tmp/mazer_home mazer install testing.foo

Will use any config in /tmp/mazer_home/, plus by default install
collections to MAZER_HOME/collections, will also now log by
default to MAZER_HOME/mazer.log and MAZER_HOME/mazer-http.log

Fixes #267
alikins added a commit that referenced this issue May 30, 2019
alikins added a commit that referenced this issue May 30, 2019
alikins added a commit that referenced this issue May 30, 2019
Move the impl details of collecting the mazer version info
for `mazer version` to ansible_galaxy.mazer_version so that
other modules can use it (namely, ansible_galaxy.cli.galaxy
for logging info at cli startup)

Fixes #267
alikins added a commit that referenced this issue May 30, 2019
And 'info' level log the exit code.

For ex:

[2019-05-30 11:17:51,249 28223 I] ansible_galaxy_cli.cli.galaxy run:236 - \
  exe="/home/adrian/venvs/mazer040test/bin/mazer" version=0.5.0 \
  config_file="/home/adrian/.ansible/mazer.yml" \
  collections_path="/home/adrian/.ansible/collections" \
  server=http://localhost:8000 action=install

Fixes #267
alikins added a commit that referenced this issue May 30, 2019
alikins added a commit that referenced this issue May 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant