Summary

Using the pretty_env_logger to add some color into the application. Considered using the crate recommended in the issue but thought that using fully-featured logger would make more sense. This entailed a few changes:

1. Introducing the log crate and an implementation of it in the form of pretty_env_logger.
2. Added a new flag --log-level (or -l for short) to allow a user to define the level. Defaults to info.
3. Updated our println!() or eprintln!() calls to use structured calls to the pretty_env_logger macros.
4. Added some emojis for flavor 🥇

Preview

Most of the changes here are visual, so here are a few example of how the CLI looks when running it.

Note: I'm not tied to any of the emojis, feel free to request that they be removed if we're not a fan. That being said, I personally like them!

Default log level:

The log level by default will be info which is intended to just display the essential information.

$ dcp quay.io/tyslaton/sample-catalog:v0.0.4 -d /tmp/dcp_test_dir

Defined log level:

By defining the log level as debug we can see a lot more of the underlying processes taking place.

$ dcp quay.io/tyslaton/sample-catalog:v0.0.4 -d /tmp/dcp_test_dir --log-level debug

Error output

$ dcp quay.io/tyslaton/sample-catalog:v0.0. -d /tmp/dcp_test_dir

Closes #15
Closes #3