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
please excuse my ignorance as I am new to the pact approach. perhaps there is something I am missing in the recommended workflow.
it seems like during normal local development, I may run my test suite without any interest in collecting pact-mock-service.log files
ultimately I suppose I could .gitignore these files in each consumer service... but it seems like it would be nice if I could provide something to pact constructor's log_dir or otherwise to opt out of the logging?
appears to be hardcoded in the start_servicecommand currently
The text was updated successfully, but these errors were encountered:
The default workflow in the majority of our repos, bar where they are shown for demonstration purposes is to .gitignore the log files and pact files which are generated each run, so they are not committed to source.
I would imagine if you did have the option, you may want to configure it from the outside, rather than having to update your code, to provide you logging by file, in the case of troubleshooting.
Does it log the same to stdout, as provided in the log file?
please excuse my ignorance as I am new to the pact approach. perhaps there is something I am missing in the recommended workflow.
it seems like during normal local development, I may run my test suite without any interest in collecting
pact-mock-service.log
filesultimately I suppose I could
.gitignore
these files in each consumer service... but it seems like it would be nice if I could provide something topact
constructor'slog_dir
or otherwise to opt out of the logging?appears to be hardcoded in the
start_service
command
currentlyThe text was updated successfully, but these errors were encountered: