User Story

As a Molecule user, I want to see the name of the current scenario in play in the Molecule-generated log messages so I can easily distinguish which scenario is generating specific log output when running multiple scenarios or debugging complex workflows.

Problem Statement

Molecule's current logging implementation mixes orchestration messages with Ansible output, making it difficult to trace which scenario is responsible for specific log entries. This is particularly problematic when:

• Running multiple scenarios in sequence
• Debugging failed test runs
• Analyzing log output from CI/CD pipelines
• Troubleshooting scenario-specific configuration issues

Solution Overview

This PR implements scenario-aware logging by:

1. Adding scenario context to all log messages using LoggerAdapter pattern
2. Reducing dependency on Rich for core logging while preserving colored output
3. Implementing proper stream separation to maintain stderr routing for test compatibility

Technical Changes

Core Implementation

• ScenarioLoggerAdapter: Extends logging.LoggerAdapter to inject scenario names into log records via extra attributes
• MoleculeConsoleHandler: Custom handler that formats log messages with scenario context and ANSI colors
• Stream preservation: Captures original stdout/stderr before enrich.Console redirection to ensure proper test capture

Key Files Modified

src/molecule/logger.py

• Added ScenarioLoggerAdapter class for scenario context injection
• Implemented MoleculeConsoleHandler with direct original stream access
• Added get_scenario_logger() convenience function
• Updated all command classes to use scenario-aware loggers

src/molecule/console.py

• Captured original_stdout and original_stderr before Console object initialization
• Preserved access to original streams for logger use

Multiple command/provisioner/verifier classes

• Updated __init__ methods to use logger.get_scenario_logger(__name__, scenario_name)
• Consistent scenario context across all Molecule components

Enrich Compatibility

The implementation specifically addresses enrich.Console(redirect=True) behavior:

• Problem: Enrich redirects all stdout/stderr through Rich's formatting pipeline
• Impact: Tests expecting stderr output fail when logs are redirected to stdout
• Solution: Access original streams captured before Console initialization
• Benefit: Maintains Rich's output capture for user experience while preserving stderr for test compatibility

Output Examples

Before

INFO     Running default > create
WARNING  Skipping, instances already created
ERROR    Failed to connect to instance

After

INFO     [default] Running default > create
WARNING  [default] Skipping, instances already created
ERROR    [default] Failed to connect to instance
INFO     [production] Running production > converge

Testing

• ✅ All existing unit tests pass (37/37)
• ✅ Integration tests maintain proper stream separation (27/28 pass, 1 unrelated failure)
• ✅ Pre-commit hooks pass (linting, type checking, formatting)
• ✅ Manual testing confirms scenario names appear in real usage
• ✅ Backward compatibility maintained for existing log consumers

Breaking Changes

None. The changes are additive and maintain full backward compatibility.

Performance Impact

Minimal. The LoggerAdapter pattern adds negligible overhead, and direct stream access is more efficient than the previous redirect manipulation approach.