bitranox-template-py-cli 2.2.0__tar.gz → 2.4.0__tar.gz

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/CHANGELOG.md

@@ -6,6 +6,36 @@ the [Keep a Changelog](https://keepachangelog.com/) format.
 
 ## [Unreleased]
 
+## [2.4.0] 2026-10-08 17:34:36
+
+### Changed
+- **The email commands' SMTP options reach the configuration as a typed `EmailConfigOverrides`
+  model instead of a plain dict.** `EmailConfigOverrides.from_cli_options(...)` takes the Click
+  values (an option that was not given is `None`, an unset `--smtp-host` an empty tuple) and
+  `apply_validated_overrides` merges only the options that were given. Its fields carry
+  EmailConfig's own names, so a field EmailConfig renames is refused instead of slipping through,
+  and `--smtp-password` is a `SecretStr` from the moment it is read; the model is a btx_lib_mail
+  `SecretSafeModel`, so a refused password never appears in a validation error's details.
+  `filter_sentinels` is gone; the command line behaves as before.
+- Requires `pydantic>=2.14.0` (and `virtualenv>=21.14.6` in the dev extra).
+
+## [2.3.0] 2026-10-08 16:14:12
+
+### Changed
+- **`config --profile NAME` checks the profile's logging settings instead of restarting logging.**
+  The check now runs through lib_log_rich's `validate_config`, which refuses exactly what starting
+  logging refuses, with the same `Error:` lines and exit 78, so nothing changes for an invalid
+  setting. What changes: the running logging runtime is no longer shut down and started again, so
+  the rest of the command keeps logging with the settings logging started with (not the profile's),
+  and a `main()` call from a worker thread no longer replaces the logging every other thread uses.
+  The `RestartLogging` port is now `CheckLoggingConfig` (`AppServices.check_logging_config`; the
+  testing composition's double refuses nothing). Requires `lib_log_rich>=6.4.2`.
+
+### Fixed
+- **A logging refusal no single setting owns reads `lib_log_rich: <reason>`.** Such a problem (for
+  example TLS together with UDP for Graylog, which lib_log_rich 6.4.2 now refuses up front) has no
+  key, and its `Error:` line came out as `lib_log_rich.: <reason>` with a dangling dot.
+
 ## [2.2.0] 2026-10-08 13:56:49
 
 ### Removed

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: bitranox_template_py_cli
-Version: 2.2.0
+Version: 2.4.0
 Summary: Template CLI application with configuration management and structured logging
 Project-URL: Homepage, https://github.com/bitranox/bitranox_template_py_cli
 Project-URL: Repository, https://github.com/bitranox/bitranox_template_py_cli.git
@@ -25,9 +25,9 @@ Requires-Dist: btx-lib-mail>=4.0.0
 Requires-Dist: click>=8.5.0
 Requires-Dist: lib-cli-exit-tools>=2.4.0
 Requires-Dist: lib-layered-config>=7.0.1
-Requires-Dist: lib-log-rich>=6.3.9
+Requires-Dist: lib-log-rich>=6.4.2
 Requires-Dist: orjson>=3.13.0
-Requires-Dist: pydantic>=2.13.5
+Requires-Dist: pydantic>=2.14.0
 Requires-Dist: python-dotenv>=1.2.4
 Requires-Dist: rich-click>=1.9.9
 Provides-Extra: dev
@@ -49,7 +49,7 @@ Requires-Dist: ruff>=0.16.10; extra == 'dev'
 Requires-Dist: textual>=8.2.8; extra == 'dev'
 Requires-Dist: twine>=7.0.0; extra == 'dev'
 Requires-Dist: urllib3>=2.8.0; extra == 'dev'
-Requires-Dist: virtualenv>=21.14.5; extra == 'dev'
+Requires-Dist: virtualenv>=21.14.6; extra == 'dev'
 Requires-Dist: wheel>=0.48.0; extra == 'dev'
 Description-Content-Type: text/markdown
 

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/docs/systemdesign/module_reference.md

@@ -26,21 +26,22 @@ moves or removes a module, a CLI option or a public name.
 - `src/bitranox_template_py_cli/adapters/email/transport.py`  -  `send_email` / `send_notification` over btx_lib_mail
 - `src/bitranox_template_py_cli/adapters/email/sender.py`  -  Re-exports of `config.py` and `transport.py`
 - `src/bitranox_template_py_cli/adapters/email/validation.py`  -  Email recipient validation
-- `src/bitranox_template_py_cli/adapters/logging/setup.py`  -  lib_log_rich initialization; takes only the `LOG_*` lines of a `.env`, and raises `InvalidLoggingConfigError` for a refused `[lib_log_rich]` value or `LOG_*` variable, after starting logging with its defaults (and without the `LOG_*` variables only when one of them is refused); `restart_logging` shuts the running runtime down and starts it again with another configuration
+- `src/bitranox_template_py_cli/adapters/logging/setup.py`  -  lib_log_rich initialization; takes only the `LOG_*` lines of a `.env`, and raises `InvalidLoggingConfigError` for a refused `[lib_log_rich]` value or `LOG_*` variable, after starting logging with its defaults (and without the `LOG_*` variables only when one of them is refused); `check_logging_config` refuses another configuration's logging settings through lib_log_rich's `validate_config`, without touching the running runtime
 - `src/bitranox_template_py_cli/adapters/cli/`  -  CLI adapter package:
   - `__init__.py`  -  Public facade
   - `constants.py`  -  Shared constants
   - `safe_console.py`  -  Encode-safe terminal output; use `safe_console.echo` instead of `click.echo`
   - `exit_codes.py`  -  POSIX exit codes (ExitCode IntEnum)
   - `context.py`  -  Click context helpers
-  - `config_load.py`  -  Configuration load for the CLI; records a load failure, `require_config` refuses with exit 78, `restart_logging` restarts logging with a configuration reloaded by `config --profile`, refusing its logging settings as the root does
+  - `config_load.py`  -  Configuration load for the CLI; records a load failure, `require_config` refuses with exit 78, `check_logging` checks the logging settings of a configuration reloaded by `config --profile`, refusing them as the root does
   - `root.py`  -  Root command group
   - `main.py`  -  Entry point
   - `typed_click.py`  -  Strictly typed wrappers for rich_click's `option`, `version_option` and `get_current_context`
   - `commands/info.py`  -  info, hello, fail commands
   - `commands/config.py`  -  config, config-deploy, config-generate-examples commands
   - `commands/email/`  -  Email commands package:
-    - `_common.py`  -  Shared SMTP override options, config loading and error-to-exit-code mapping
+    - `_common.py`  -  Shared SMTP override options and their typed `EmailConfigOverrides`, config
+      loading and error-to-exit-code mapping
     - `send_email.py`  -  send-email command
     - `send_notification.py`  -  send-notification command
   - `commands/logging.py`  -  logdemo command
@@ -409,7 +410,7 @@ The `adapters/memory/` package provides lightweight implementations for testing:
 |---------------------|-----------------------------------------------------------------------------|
 | `memory/config.py`  | `GetConfig`, `GetDefaultConfigPath`, `DeployConfiguration`, `DisplayConfig` |
 | `memory/email.py`   | `SendEmail`, `SendNotification`                                             |
-| `memory/logging.py` | `InitLogging`, `RestartLogging`                                             |
+| `memory/logging.py` | `InitLogging`, `CheckLoggingConfig`                                         |
 
 `adapters/memory` exports `EmailSpy` (from `memory/email.py`): its `send_email` and
 `send_notification` methods satisfy the email ports and record each call as a `CapturedEmail` /

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "bitranox_template_py_cli"
-version = "2.2.0"
+version = "2.4.0"
 description = "Template CLI application with configuration management and structured logging"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -9,11 +9,12 @@ dependencies = [
     # Imported directly (adapters/cli/main.py, commands/config.py), not only through rich-click.
     "click>=8.5.0",
     "lib_cli_exit_tools>=2.4.0",
-    "lib_log_rich>=6.3.9",
+    # 6.4.2: validate_config, the check config --profile runs, refuses exactly what init() refuses.
+    "lib_log_rich>=6.4.2",
     "python-dotenv>=1.2.4",
     "lib_layered_config>=7.0.1",
     "btx_lib_mail>=4.0.0",
-    "pydantic>=2.13.5",
+    "pydantic>=2.14.0",
     "orjson>=3.13.0",
 ]
 license = { text = "MIT" }
@@ -76,7 +77,7 @@ dev = [
   "wheel>=0.48.0",               # CVE-2025-24049
   "pynacl>=1.6.2",               # CVE-2025-69277
   "urllib3>=2.8.0",              # CVE-2025-66471, CVE-2025-66418
-  "virtualenv>=21.14.5",         # CVE-2025-22702
+  "virtualenv>=21.14.6",         # CVE-2025-22702
 ]
 
 [project.scripts]

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/__init__conf__.py

@@ -40,7 +40,7 @@ name = "bitranox_template_py_cli"
 #: Human-readable summary shown in CLI help output.
 title = "Template CLI application with configuration management and structured logging"
 #: Current release version pulled from ``pyproject.toml`` by automation.
-version = "2.2.0"
+version = "2.4.0"
 #: Repository homepage presented to users.
 homepage = "https://github.com/bitranox/bitranox_template_py_cli"
 #: Author attribution surfaced in CLI output.

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/cli/commands/config.py

@@ -32,7 +32,7 @@ from bitranox_template_py_cli.adapters.config.overrides import nest_overrides
 from bitranox_template_py_cli.domain.enums import DeployTarget, OutputFormat
 
 from .. import safe_console
-from ..config_load import load_config, report_load_failure, require_config, restart_logging
+from ..config_load import check_logging, load_config, report_load_failure, require_config
 from ..constants import CLICK_CONTEXT_SETTINGS
 from ..context import CLIContext, get_cli_context
 from ..exit_codes import ExitCode
@@ -110,8 +110,8 @@ def _resolve_config(ctx: click.Context, cli_ctx: CLIContext, profile: str | None
 
     When a subcommand-level profile override is specified, reloads config
     with that profile, the root's ``--env-file`` and any root-level ``--set``
-    overrides stored in the CLI context, and restarts logging with it, which
-    refuses its logging settings the way the root refuses its own.
+    overrides stored in the CLI context, and checks its logging settings, which
+    are refused the way the root refuses its own; logging itself keeps running unchanged.
 
     Args:
         ctx: The running command's click context, exited with 78 when loading failed.
@@ -128,7 +128,7 @@ def _resolve_config(ctx: click.Context, cli_ctx: CLIContext, profile: str | None
         cli_ctx.services, profile=profile, env_file=cli_ctx.env_file, set_overrides=cli_ctx.set_overrides
     )
     if error is None:
-        error = restart_logging(cli_ctx.services, config, env_file=cli_ctx.env_file)
+        error = check_logging(cli_ctx.services, config)
     if error is not None:
         report_load_failure(error, show_traceback=cli_ctx.traceback)
         ctx.exit(ExitCode.CONFIG_ERROR)

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/cli/commands/email/__init__.py

@@ -5,12 +5,13 @@ Provides commands for sending emails and notifications via SMTP.
 Contents:
     * :func:`.send_email.cli_send_email` - Send email with optional HTML and attachments.
     * :func:`.send_notification.cli_send_notification` - Send simple plain-text notification.
+    * :class:`._common.EmailConfigOverrides` - The SMTP options a command line gave, typed.
 """
 
 from __future__ import annotations
 
-from ._common import filter_sentinels
+from ._common import EmailConfigOverrides
 from .send_email import cli_send_email
 from .send_notification import cli_send_notification
 
-__all__ = ["cli_send_email", "cli_send_notification", "filter_sentinels"]
+__all__ = ["EmailConfigOverrides", "cli_send_email", "cli_send_notification"]

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/cli/commands/email/_common.py

@@ -9,10 +9,10 @@ from __future__ import annotations
 import functools
 import logging
 import os
-from typing import TYPE_CHECKING, Any, NoReturn, cast
+from typing import TYPE_CHECKING, Any, NoReturn
 
-from btx_lib_mail import AttachmentSecurityError
-from pydantic import ValidationError
+from btx_lib_mail import AttachmentSecurityError, SecretSafeModel
+from pydantic import ConfigDict, SecretStr, ValidationError
 
 from bitranox_template_py_cli import __init__conf__
 from bitranox_template_py_cli.adapters.email.config import describe_validation_error
@@ -33,51 +33,79 @@ if TYPE_CHECKING:
 logger = logging.getLogger(__name__)
 
 
-def filter_sentinels(**kwargs: Any) -> dict[str, Any]:
-    """Filter out None and empty tuple sentinels, converting tuples to lists.
+class EmailConfigOverrides(SecretSafeModel):
+    """The EmailConfig fields the command line overrides; ``None`` means the option was not given.
 
-    Used to prepare CLI option overrides for ``_apply_validated_overrides()``.
-    Removes None values (unset options) and empty tuples (unset multiple options),
-    and converts non-empty tuples to lists for Pydantic compatibility.
+    Each field carries EmailConfig's own name, so a field EmailConfig renames is refused here
+    instead of being passed along unnoticed. The password stays a ``SecretStr`` from the moment
+    the command line hands it over, and a validation error never carries its value, not even in
+    ``errors()`` or ``json()``.
+    """
 
-    Args:
-        **kwargs: Keyword arguments to filter.
+    model_config = ConfigDict(frozen=True, extra="forbid")
+    credential_fields = frozenset({"smtp_password"})
+
+    smtphosts: tuple[str, ...] | None = None
+    smtp_username: str | None = None
+    smtp_password: SecretStr | None = None
+    smtp_use_starttls: bool | None = None
+    smtp_timeout: float | None = None
+    raise_on_missing_attachments: bool | None = None
+    raise_on_invalid_recipient: bool | None = None
+
+    @classmethod
+    def from_cli_options(
+        cls,
+        *,
+        smtp_hosts: tuple[str, ...] = (),
+        smtp_username: str | None = None,
+        smtp_password: str | None = None,
+        use_starttls: bool | None = None,
+        timeout: float | None = None,
+        raise_on_missing_attachments: bool | None = None,
+        raise_on_invalid_recipient: bool | None = None,
+    ) -> EmailConfigOverrides:
+        """Build the overrides from the values Click hands a command.
+
+        Click reports an option that was not given as ``None``, and a ``multiple=True`` option
+        that was not given as an empty tuple; both become ``None`` here.
+
+        Examples:
+            >>> EmailConfigOverrides.from_cli_options(smtp_hosts=(), timeout=5.0).model_dump(exclude_none=True)
+            {'smtp_timeout': 5.0}
+        """
+        return cls(
+            smtphosts=smtp_hosts or None,
+            smtp_username=smtp_username,
+            smtp_password=None if smtp_password is None else SecretStr(smtp_password),
+            smtp_use_starttls=use_starttls,
+            smtp_timeout=timeout,
+            raise_on_missing_attachments=raise_on_missing_attachments,
+            raise_on_invalid_recipient=raise_on_invalid_recipient,
+        )
 
-    Returns:
-        Filtered dict with sentinel values removed and tuples converted to lists.
-    """
-    result: dict[str, Any] = {}
-    for k, v in kwargs.items():
-        if v is None or v == ():
-            continue
-        if isinstance(v, tuple):
-            result[k] = list(cast("tuple[Any, ...]", v))
-        else:
-            result[k] = v
-    return result
-
-
-def apply_validated_overrides(base_config: EmailConfig, overrides: dict[str, Any]) -> EmailConfig:
+
+def apply_validated_overrides(base_config: EmailConfig, overrides: EmailConfigOverrides) -> EmailConfig:
     """Apply overrides with full Pydantic validation.
 
-    Uses model_validate() with a merged dict instead of model_copy(update=...)
-    to ensure Pydantic validators run on all overridden values.
+    Uses model_validate() with a merged mapping instead of model_copy(update=...)
+    to ensure EmailConfig's validators run on all overridden values.
 
     Args:
         base_config: Base EmailConfig to merge overrides into.
-        overrides: Dict of field values to override (already filtered).
+        overrides: The options given on the command line.
 
     Returns:
-        New EmailConfig with overrides applied and validated.
+        ``base_config`` itself when no option was given, else a new EmailConfig with the
+        overrides applied and validated.
 
     Raises:
         ValidationError: When overrides contain invalid values.
     """
-    if not overrides:
+    given = overrides.model_dump(exclude_none=True)
+    if not given:
         return base_config
-    base_dict = base_config.model_dump()
-    merged = {**base_dict, **overrides}
-    return EmailConfig.model_validate(merged)
+    return EmailConfig.model_validate({**base_config.model_dump(), **given})
 
 
 def smtp_config_options(func: Callable[..., Any]) -> Callable[..., Any]:
@@ -337,9 +365,9 @@ def _handle_send_error(
 
 
 __all__ = [
+    "EmailConfigOverrides",
     "apply_validated_overrides",
     "execute_with_email_error_handling",
-    "filter_sentinels",
     "handle_validation_error",
     "load_and_validate_email_config",
     "smtp_config_options",

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/cli/commands/email/send_email.py

@@ -18,9 +18,9 @@ from ...constants import CLICK_CONTEXT_SETTINGS
 from ...context import get_cli_context
 from ...typed_click import option
 from ._common import (
+    EmailConfigOverrides,
     apply_validated_overrides,
     execute_with_email_error_handling,
-    filter_sentinels,
     handle_validation_error,
     load_and_validate_email_config,
     smtp_config_options,
@@ -112,12 +112,12 @@ def cli_send_email(
 
     with lib_log_rich.runtime.bind(job_id="cli-send-email", extra=extra):
         email_config = load_and_validate_email_config(config, cli_ctx.services.load_email_config_from_dict)
-        overrides = filter_sentinels(
-            smtphosts=smtp_hosts,
+        overrides = EmailConfigOverrides.from_cli_options(
+            smtp_hosts=smtp_hosts,
             smtp_username=smtp_username,
             smtp_password=smtp_password,
-            smtp_use_starttls=use_starttls,
-            smtp_timeout=timeout,
+            use_starttls=use_starttls,
+            timeout=timeout,
             raise_on_missing_attachments=raise_on_missing_attachments,
             raise_on_invalid_recipient=raise_on_invalid_recipient,
         )

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/cli/commands/email/send_notification.py

@@ -17,9 +17,9 @@ from ...constants import CLICK_CONTEXT_SETTINGS
 from ...context import get_cli_context
 from ...typed_click import option
 from ._common import (
+    EmailConfigOverrides,
     apply_validated_overrides,
     execute_with_email_error_handling,
-    filter_sentinels,
     handle_validation_error,
     load_and_validate_email_config,
     smtp_config_options,
@@ -70,12 +70,12 @@ def cli_send_notification(
 
     with lib_log_rich.runtime.bind(job_id="cli-send-notification", extra=extra):
         email_config = load_and_validate_email_config(config, cli_ctx.services.load_email_config_from_dict)
-        overrides = filter_sentinels(
-            smtphosts=smtp_hosts,
+        overrides = EmailConfigOverrides.from_cli_options(
+            smtp_hosts=smtp_hosts,
             smtp_username=smtp_username,
             smtp_password=smtp_password,
-            smtp_use_starttls=use_starttls,
-            smtp_timeout=timeout,
+            use_starttls=use_starttls,
+            timeout=timeout,
             raise_on_invalid_recipient=raise_on_invalid_recipient,
         )
         try:

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/cli/config_load.py

@@ -16,7 +16,7 @@ Contents:
     * :func:`load_config` - load with profile, ``.env`` and ``--set``, or say why not.
     * :func:`start_logging` - start logging; an invalid ``[lib_log_rich]`` value or ``LOG_*``
       variable is a load failure.
-    * :func:`restart_logging` - the same refusal for a configuration loaded after logging started.
+    * :func:`check_logging` - the same refusal for a configuration loaded after logging started.
     * :func:`require_config` - the configuration, or exit 78 naming the failure.
     * :func:`report_load_failure` - the one-line report, after the traceback on request.
     * :func:`echo_load_traceback` - the loader's traceback alone, for a caller with its own line.
@@ -105,7 +105,8 @@ def start_logging(
     refused setting) before it raises, and the commands that read the configuration refuse with
     exit 78 and the refusal: ``lib_log_rich.<key>: <reason>`` for a problem the section's type
     check finds, lib_log_rich's own message for a value only lib_log_rich refuses, whether it
-    came from the section or a ``LOG_*`` variable (``lib_log_rich: Unknown log level: 'bogus'``).
+    came from the section or a ``LOG_*`` variable (``lib_log_rich: Invalid runtime settings:
+    console_level: Unknown log level: 'bogus'``).
 
     Args:
         services: The composition's services; only ``init_logging`` is used.
@@ -124,25 +125,24 @@ def start_logging(
     return config, config_error
 
 
-def restart_logging(services: AppServices, config: Config, *, env_file: str | None) -> Exception | None:
-    """Restart logging with a configuration loaded after it started; a refused setting is returned.
+def check_logging(services: AppServices, config: Config) -> Exception | None:
+    """Judge the logging settings of a configuration loaded after logging started; a refusal is returned.
 
     ``config --profile`` reloads the configuration once logging is running, so
     :func:`start_logging` never sees the reloaded ``[lib_log_rich]`` section; without this an
-    invalid value there would display with exit 0 while plain ``config`` exits 78. Restarting
-    runs the very start :func:`start_logging` ran, so it refuses the same settings in the same
-    words, and the rest of the command logs with the reloaded settings.
+    invalid value there would display with exit 0 while plain ``config`` exits 78. The check
+    refuses what :func:`start_logging` refuses, in the same words, and never touches the
+    running runtime: the command keeps logging with the settings logging started with.
 
     Args:
-        services: The composition's services; only ``restart_logging`` is used.
+        services: The composition's services; only ``check_logging_config`` is used.
         config: The configuration :func:`load_config` returned.
-        env_file: The ``--env-file`` path, or None; logging reads its ``LOG_*`` lines from it.
 
     Returns:
-        None, or the refusal; logging then runs with its defaults.
+        None, or the refusal.
     """
     try:
-        services.restart_logging(config, dotenv_path=env_file)
+        services.check_logging_config(config)
     except InvalidLoggingConfigError as exc:
         return exc
     return None
@@ -196,10 +196,10 @@ def require_config(ctx: click.Context, cli_ctx: CLIContext) -> Config:
 
 
 __all__ = [
+    "check_logging",
     "echo_load_traceback",
     "load_config",
     "report_load_failure",
     "require_config",
-    "restart_logging",
     "start_logging",
 ]

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/logging/setup.py

@@ -7,7 +7,7 @@ eliminating duplication between module entry (__main__.py) and console script
 Contents:
     * :func:`init_logging` - idempotent logging initialization from the ``[lib_log_rich]``
       section and the ``LOG_*`` variables (the environment, plus the ``LOG_*`` lines of a ``.env``).
-    * :func:`restart_logging` - stop the running runtime and start it again with another configuration.
+    * :func:`check_logging_config` - refuse another configuration's logging settings without touching the runtime.
     * :class:`InvalidLoggingConfigError` - the ``[lib_log_rich]`` section or a ``LOG_*`` variable
       cannot configure logging.
     * :func:`_build_runtime_config` - constructs RuntimeConfig from layered sources.
@@ -100,10 +100,12 @@ class InvalidLoggingConfigError(ConfigurationError):
     """lib_log_rich refuses its settings: one ``<key>: <reason>`` in :attr:`problems` per problem.
 
     The settings are the ``[lib_log_rich]`` section plus any ``LOG_*`` variable. A problem the
-    type check of the section finds names the key and never repeats the refused value. A value
-    only lib_log_rich itself refuses, such as an unknown level in ``LOG_CONSOLE_LEVEL`` or in the
-    section's ``console_level``, is reported in lib_log_rich's own words (``lib_log_rich: Unknown
-    log level: 'bogus'``), which may name neither the setting nor where it was set.
+    type check of the section finds names the key and never repeats the refused value; one no
+    single key owns (TLS over UDP for Graylog) reads ``lib_log_rich: <reason>``. A value only
+    lib_log_rich itself refuses, such as an unknown level in ``LOG_CONSOLE_LEVEL`` or in the
+    section's ``console_level``, is reported in lib_log_rich's own words, which name the setting
+    and repeat the value (``lib_log_rich: Invalid runtime settings: console_level: Unknown log
+    level: 'bogus'``).
 
     Attributes:
         problems: One line per refused setting.
@@ -128,15 +130,33 @@ _PROJECT_MARKERS = ("pyproject.toml", ".git")
 
 
 def _problems(error: BaseException) -> list[str]:
-    """One line per problem, from the first pydantic error in ``error``'s chain; never the value."""
+    """One line per problem: key and reason from the first pydantic error in ``error``'s chain.
+
+    A pydantic problem never repeats the refused value; one no single key owns (a model-wide
+    check) has no key and reads ``lib_log_rich: <reason>``. Without a pydantic error in the chain,
+    the line is lib_log_rich's own first line, which may repeat the value
+    (``Invalid runtime settings: console_level: Unknown log level: 'bogus'``).
+    """
     cause: BaseException | None = error
     while cause is not None and not isinstance(cause, ValidationError):
         cause = cause.__cause__ or cause.__context__
     if cause is None:
         # Not a pydantic error (e.g. an unknown level name in a LOG_* variable): lib_log_rich's
-        # own first line, which may name neither the variable nor where it was set.
+        # own first line.
         return [f"lib_log_rich: {str(error).splitlines()[0]}"]
-    return [f"lib_log_rich.{'.'.join(str(part) for part in item['loc'])}: {item['msg']}" for item in cause.errors()]
+    return [f"{_problem_key(item['loc'])}: {item['msg']}" for item in cause.errors()]
+
+
+def _problem_key(loc: tuple[int | str, ...]) -> str:
+    """``lib_log_rich.<key>`` for a problem located at a key, bare ``lib_log_rich`` for a model-wide one.
+
+    Example:
+        >>> _problem_key(("rate_limit",))
+        'lib_log_rich.rate_limit'
+        >>> _problem_key(())
+        'lib_log_rich'
+    """
+    return ".".join(["lib_log_rich", *(str(part) for part in loc)])
 
 
 def _nearest_dotenv() -> Path | None:
@@ -281,35 +301,39 @@ def init_logging(config: Config, *, dotenv_path: str | None = None) -> None:
     lib_log_rich.runtime.attach_std_logging()
 
 
-def restart_logging(config: Config, *, dotenv_path: str | None = None) -> None:
-    """Stop the running lib_log_rich runtime, then start it again with ``config``.
+def check_logging_config(config: Config) -> None:
+    """Refuse ``config``'s logging settings as :func:`init_logging` would, without touching the runtime.
 
     :func:`init_logging` returns at once while a runtime is running, so a configuration loaded
     after logging started (``config --profile``'s reload) would never have its logging settings
-    judged. This runs that same start again: a setting lib_log_rich refuses raises exactly as it
-    does there, and logging is left running with the defaults. lib_log_rich has no public call
-    that checks settings without starting the runtime.
+    judged. lib_log_rich's ``validate_config`` refuses exactly what its ``init`` refuses, with the
+    same message and the same ``LOG_*`` overrides, and neither reads nor replaces the running
+    runtime, so logging keeps running with the settings it started with, on every thread.
 
     Args:
         config: Already-loaded layered configuration object.
-        dotenv_path: As for :func:`init_logging`.
 
     Raises:
-        InvalidLoggingConfigError: As for :func:`init_logging`.
+        InvalidLoggingConfigError: As for :func:`init_logging`, with the same problem lines.
 
-    Side Effects:
-        Flushes and shuts down the running runtime first (its queue, Graylog and journald
-        adapters included); the new one carries ``config``'s logging settings.
+    Example:
+        >>> check_logging_config(Config({"lib_log_rich": {"console_level": "info"}}, {}))
+        >>> try:
+        ...     check_logging_config(Config({"lib_log_rich": {"rate_limit": "100:60"}}, {}))
+        ... except InvalidLoggingConfigError as exc:
+        ...     print(exc)
+        lib_log_rich.rate_limit: Input should be a valid tuple
     """
-    if lib_log_rich.runtime.is_initialised():
-        lib_log_rich.runtime.shutdown()
-    init_logging(config, dotenv_path=dotenv_path)
+    try:
+        lib_log_rich.runtime.validate_config(_build_runtime_config(config))
+    except ValueError as exc:  # pydantic's ValidationError is a ValueError
+        raise InvalidLoggingConfigError(_problems(exc)) from exc
 
 
 __all__ = [
     "InvalidLoggingConfigError",
     "LoggingConfigModel",
+    "check_logging_config",
     "init_logging",
     "log_variables_hidden",
-    "restart_logging",
 ]

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/memory/__init__.py

@@ -20,28 +20,28 @@ from .config import (
     get_default_config_path_in_memory,
 )
 from .email import EmailSpy
-from .logging import init_logging_in_memory, restart_logging_in_memory
+from .logging import check_logging_config_in_memory, init_logging_in_memory
 
 # Static conformance assertions
 if TYPE_CHECKING:
     from bitranox_template_py_cli.application.ports import (
+        CheckLoggingConfig,
         GetConfig,
         GetDefaultConfigPath,
         InitLogging,
-        RestartLogging,
     )
 
     _assert_get_config: GetConfig = get_config_in_memory
     _assert_get_default_config_path: GetDefaultConfigPath = get_default_config_path_in_memory
     _assert_init_logging: InitLogging = init_logging_in_memory
-    _assert_restart_logging: RestartLogging = restart_logging_in_memory
+    _assert_check_logging_config: CheckLoggingConfig = check_logging_config_in_memory
 
 __all__ = [
     "EmailSpy",
+    "check_logging_config_in_memory",
     "deploy_configuration_in_memory",
     "display_config_in_memory",
     "get_config_in_memory",
     "get_default_config_path_in_memory",
     "init_logging_in_memory",
-    "restart_logging_in_memory",
 ]

{bitranox_template_py_cli-2.2.0 → bitranox_template_py_cli-2.4.0}/src/bitranox_template_py_cli/adapters/memory/logging.py

@@ -63,17 +63,18 @@ def init_logging_in_memory(config: Config, *, dotenv_path: str | None = None) ->
         )
 
 
-def restart_logging_in_memory(config: Config, *, dotenv_path: str | None = None) -> None:
-    """Keep the test runtime: :func:`init_logging_in_memory` ignores the configuration, so a restart changes nothing.
+def check_logging_config_in_memory(config: Config) -> None:
+    """Refuse nothing: the test runtime ignores the configuration, so no setting in it can break it.
+
+    :func:`init_logging_in_memory` starts a fixed runtime whatever the configuration holds.
 
     Args:
-        config: Unused; the parameter exists to satisfy the ``RestartLogging`` protocol.
-        dotenv_path: Unused for the same reason.
+        config: Unused; the parameter exists to satisfy the ``CheckLoggingConfig`` protocol.
 
     Example:
         >>> from lib_layered_config import Config
-        >>> restart_logging_in_memory(Config({"lib_log_rich": {"rate_limit": "100:60"}}, {}))
+        >>> check_logging_config_in_memory(Config({"lib_log_rich": {"rate_limit": "100:60"}}, {}))
     """
 
 
-__all__ = ["init_logging_in_memory", "restart_logging_in_memory"]
+__all__ = ["check_logging_config_in_memory", "init_logging_in_memory"]