yb-observability 0.1.0__tar.gz

yb_observability-0.1.0/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+/*
+@Ybouali

yb_observability-0.1.0/.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5
+
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    open-pull-requests-limit: 5

yb_observability-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,21 @@
+## Description
+
+<!-- Describe what this pull request changes and why. -->
+
+## Changes
+
+- 
+
+## Testing
+
+- [ ] `uv run pytest`
+- [ ] `uv run ruff check .`
+- [ ] `uv run ruff format --check .`
+- [ ] `uv run pyright`
+
+## Checklist
+
+- [ ] Tests added or updated where necessary
+- [ ] Documentation updated where necessary
+- [ ] No secrets or sensitive information added
+- [ ] Public API changes are intentional

yb_observability-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  quality:
+    name: Quality checks
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "0.12.5"
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install 3.14
+
+      - name: Install dependencies
+        run: uv sync --locked
+
+      - name: Run tests
+        run: uv run pytest
+
+      - name: Check linting
+        run: uv run ruff check .
+
+      - name: Check formatting
+        run: uv run ruff format --check .
+
+      - name: Run type checking
+        run: uv run pyright

yb_observability-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,60 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "0.12.5"
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install 3.14
+
+      - name: Install dependencies
+        run: uv sync --locked
+
+      - name: Run tests
+        run: uv run pytest
+
+      - name: Build package
+        run: uv build
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: distributions
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: distributions
+          path: dist/
+
+      - name: Publish package to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

yb_observability-0.1.0/.gitignore

@@ -0,0 +1,50 @@
+# Byte-compiled / optimized Python files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Python environments
+.venv/
+venv/
+env/
+ENV/
+
+# Distribution / packaging
+build/
+dist/
+*.egg-info/
+.eggs/
+
+# Pytest
+.pytest_cache/
+
+# Coverage
+.coverage
+.coverage.*
+htmlcov/
+coverage.xml
+
+# Ruff
+.ruff_cache/
+
+# Pyright
+.pyright/
+
+# IDEs
+.vscode/
+.idea/
+
+# macOS
+.DS_Store
+
+# Environment files
+.env
+.env.*
+!.env.example
+
+# Logs
+logs/
+
+# Local tooling / temporary files
+*.tmp
+*.temp

yb_observability-0.1.0/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Changelog
+
+All notable changes to `yb-observability` are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project follows Semantic Versioning.
+
+## [Unreleased]
+
+Changes that are planned or currently under development.
+
+## [0.1.0] - 2026-09-13
+
+### Added
+
+* Initial project structure.
+* Python 3.14 support.
+* YAML configuration loading.
+* Environment variable resolution for configuration values.
+* Loguru-based logging infrastructure.
+* Service-aware logging.
+* Console logging.
+* File logging.
+* Daily log rotation.
+* Configurable log retention.
+* Automated testing infrastructure.
+* Ruff configuration.
+* Pyright configuration.
+* Pytest configuration.
+
+[Unreleased]: https://github.com/Ybouali/yb-observability/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/Ybouali/yb-observability/releases/tag/v0.1.0

yb_observability-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,54 @@
+# Security Policy
+
+## Supported Versions
+
+Security fixes are generally applied to actively maintained versions of `yb-observability`.
+
+| Version              | Supported   |
+| -------------------- | ----------- |
+| Latest minor release | Yes         |
+| Older releases       | Best effort |
+| Unsupported releases | No          |
+
+Users should keep `yb-observability` up to date whenever possible.
+
+## Reporting a Vulnerability
+
+Please do **not** report security vulnerabilities through public GitHub issues.
+
+If you believe you have found a security vulnerability, report it privately through the repository's GitHub security reporting mechanism.
+
+When reporting a vulnerability, include:
+
+* A clear description of the vulnerability.
+* The affected version.
+* Steps required to reproduce the issue.
+* The potential security impact.
+* Any relevant logs, stack traces, or proof of concept that can safely be shared.
+
+Please do not include secrets, credentials, API keys, personal data, or other sensitive information in the report.
+
+## Responsible Disclosure
+
+Please allow reasonable time for the vulnerability to be investigated and addressed before publicly disclosing technical details.
+
+Security fixes may be released as a patch, minor release, or major release depending on the impact and whether the change affects the public API.
+
+## Dependency Security
+
+The project depends on third-party Python packages.
+
+Dependencies should be kept reasonably up to date, and security-related dependency updates should be addressed promptly when practical.
+
+Contributors should avoid introducing dependencies when the functionality can be implemented safely without adding unnecessary project complexity.
+
+## Scope
+
+This policy covers security vulnerabilities in:
+
+* `yb-observability` source code.
+* Build and packaging configuration.
+* Project infrastructure that can affect users of the published package.
+* Dependencies introduced directly by the project where the project configuration is responsible for the vulnerability.
+
+Application-specific security issues in software that uses `yb-observability` should be reported to the maintainers of that application.

yb_observability-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,238 @@
+# Contributing to yb-observability
+
+Thank you for contributing to `yb-observability`.
+
+The project is designed as a reusable Python library, so contributions should prioritize clear APIs, minimal coupling, backwards compatibility, and strong test coverage.
+
+## Development Requirements
+
+The project currently uses:
+
+* Python 3.14
+* uv
+* Pytest
+* Ruff
+* Pyright
+
+Clone the repository and enter the project:
+
+```bash
+git clone <repository-url>
+cd yb-observability
+```
+
+Install the development environment:
+
+```bash
+uv sync
+```
+
+## Project Structure
+
+```text
+src/yb_observability/
+├── config/
+└── logging/
+
+tests/
+├── config/
+└── logging/
+```
+
+Implementation code belongs under `src/yb_observability/`.
+
+Tests belong under the corresponding directory in `tests/`.
+
+For example:
+
+```text
+src/yb_observability/config/loader.py
+tests/config/test_loader.py
+```
+
+## Development Workflow
+
+Create a branch for your work:
+
+```bash
+git switch -c feature/my-feature
+```
+
+Make the changes and add tests where appropriate.
+
+Run the complete test suite:
+
+```bash
+uv run pytest
+```
+
+Run Ruff:
+
+```bash
+uv run ruff check .
+```
+
+Check formatting:
+
+```bash
+uv run ruff format --check .
+```
+
+Run Pyright:
+
+```bash
+uv run pyright
+```
+
+All checks should pass before opening a pull request.
+
+## Code Style
+
+Follow the project's Ruff configuration.
+
+The project uses:
+
+* 88-character line length.
+* Double quotes.
+* Four spaces for indentation.
+* Python 3.14 syntax and typing features where appropriate.
+
+Prefer simple and explicit implementations over unnecessary abstractions.
+
+## Public API
+
+Changes to the public API should be made carefully.
+
+Before adding a public class, function, or module, consider whether it is genuinely useful to library consumers.
+
+Avoid exposing implementation details unnecessarily.
+
+For example, prefer a stable public API such as:
+
+```python
+from yb_observability.config import ConfigLoader
+```
+
+rather than requiring consumers to import internal implementation modules.
+
+## Tests
+
+New functionality should include tests.
+
+Tests should verify observable behavior rather than implementation details.
+
+For bug fixes, add a regression test whenever practical.
+
+The test suite can be run with:
+
+```bash
+uv run pytest
+```
+
+## Documentation
+
+Public functionality should be documented.
+
+Documentation should explain:
+
+* What the feature does.
+* Why it exists.
+* How to use it.
+* Important configuration or behavioral constraints.
+
+Architectural decisions should be documented separately when they affect the design of the library.
+
+## Commit Messages
+
+Use clear, descriptive commit messages.
+
+The project follows Conventional Commits.
+
+Examples:
+
+```text
+feat(config): add environment variable resolution
+fix(config): handle invalid YAML
+feat(logging): add daily file rotation
+test(config): add nested environment tests
+docs(logging): document retention configuration
+refactor(logging): simplify handler configuration
+```
+
+Common commit types include:
+
+```text
+feat
+fix
+docs
+test
+refactor
+chore
+ci
+```
+
+## Pull Requests
+
+Pull requests should:
+
+* Explain what changed.
+* Explain why the change was needed.
+* Include tests for new behavior.
+* Keep unrelated changes out of the pull request.
+* Pass all automated checks.
+
+Keep pull requests focused. A feature, bug fix, or refactor should normally be submitted separately rather than combining unrelated changes.
+
+## Backwards Compatibility
+
+`yb-observability` is a reusable library, so backwards compatibility is important.
+
+Breaking changes to public APIs should:
+
+1. Be clearly identified.
+2. Be documented.
+3. Include an appropriate version change.
+4. Explain the migration path when possible.
+
+The project follows semantic versioning:
+
+```text
+MAJOR.MINOR.PATCH
+```
+
+For example:
+
+```text
+0.1.0
+0.2.0
+0.2.1
+```
+
+While the project remains below `1.0.0`, the public API may evolve more quickly, but breaking changes should still be intentional and documented.
+
+## Issues
+
+Before opening an issue:
+
+* Search existing issues.
+* Verify that the behavior is reproducible.
+* Include relevant error messages and environment information.
+* Provide a minimal reproduction when reporting a bug.
+
+Do not include secrets, credentials, API keys, or other sensitive information in issues.
+
+## Security Issues
+
+Do not report security vulnerabilities through public GitHub issues.
+
+See `SECURITY.md` for the security reporting process.
+
+## Code of Conduct
+
+All contributors are expected to follow the project's `CODE_OF_CONDUCT.md`.
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under the same license as the project.
+
+`yb-observability` is distributed under the MIT License.