Setup Python logging with configurable verbosity

[Copilot]

Configures Python logging for the project with a structured format and CLI-controlled verbosity.

Changes

Logging configuration (src/dab_project/logging_config.py)

• Centralized setup_logging() function with format: YYYY-MM-DD HH:MM:SS,mmm - LEVEL - module - message
• INFO level by default; DEBUG when verbose flag enabled
• Console handler on stdout (extensible for future file logging)

CLI integration (src/dab_project/cli.py)

• Added -v/--verbose flag to enable DEBUG logging
• Replaced print() error handling with logger.error()
• Calls setup_logging() on startup

Example output

# Without -v flag (INFO level)
$ dab-project InvalidTask
2026-01-06 10:26:52,599 - ERROR - dab_project.cli - Error with component 'InvalidTask': Unknown Task...

# With -v flag (DEBUG level)
$ dab-project -v BronzeTaxiTask
2026-01-06 10:27:15,123 - INFO - dab_project.tasks.base_task - Starting ETL task: BronzeTaxiTask
2026-01-06 10:27:15,124 - DEBUG - dab_project.tasks.base_task - Task class: dab_project.tasks.bronze_nyctaxi.BronzeTaxiTask

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• astral.sh
  • Triggering command: /usr/bin/curl curl -LsSf REDACTED (dns block)
• repos.spark-packages.org
  • Triggering command: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java -cp hive-jackson/*:/home/REDACTED/work/databricks-bundle-implementation/databricks-bundle-implementation/.venv/lib/python3.12/site-packages/pyspark/conf:/home/REDACTED/work/databricks-bundle-implementation/databricks-bundle-implementation/.venv/lib/python3.12/sit /tmp/cciIv9rb.s (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Setup Python logging</issue_title>
<issue_description>Currently we do not configure how the Python project handles logging.
I want logs to look like this example I found 2025-04-23 10:35:42,789 - INFO - auth - User login successful.
By default, INFO (and higher) should be logged. DEBUG should only be logged if we add the cli flag -v.
Send logs to console only for now, but consider that we may log to files in the future.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Setup Python logging #20

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.