pyproject.toml

[project]
name = "redstackpro"
version = "0.9.1"
description = "Composition layer for red team infrastructure and cyber ranges"
requires-python = ">=3.11"
license = { text = "MIT" }
dependencies = [
    "pyyaml>=6.0",
    "jsonschema>=4.20",
    "fastapi>=0.110",
    "sqlalchemy>=2.0",
    "pydantic>=2.6",
]

[project.scripts]
redstackpro = "redstackpro.cli:main"

[project.optional-dependencies]
# alembic in dev to author revisions and run the drift guard; in postgres because
# a real deployment upgrades the schema on startup. The core install stays free
# of it: SQLite builds the schema from the models and never imports alembic.
dev = [
    "pytest>=8.0",
    "httpx>=0.27",
    "uvicorn[standard]>=0.27",
    "python-hcl2>=4.3",
    "alembic>=1.13",
    # The collector pipeline tests render the index template as the .j2 it is.
    "jinja2>=3.1",
]
postgres = ["psycopg[binary]>=3.1", "alembic>=1.13"]

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[tool.hatch.build.targets.wheel]
packages = ["src/redstackpro"]

# Static modules and roles ship with the package. The API needs them at runtime
# to produce a complete export, so they are package data rather than repo root
# files copied by the CLI. See 0015.
artifacts = [
    "src/redstackpro/assets/**",
    # The document schema, the registry data, and the worked examples now live in
    # the package and are resolved from it at runtime, so they ship as data too.
    "src/redstackpro/schema/**",
    # The revision template ships so `alembic revision` works from an installed
    # package. The revisions themselves are .py and are packaged already.
    "src/redstackpro/api/migrations/script.py.mako",
]

[tool.pytest.ini_options]
pythonpath = ["src"]
testpaths = ["tests"]