mockstack 0.6.1__tar.gz → 0.7.1__tar.gz

mockstack-0.7.1/.dockerignore

@@ -0,0 +1,18 @@
+*
+!mockstack
+mockstack/tests
+!dist/*-none-any.whl
+!MANIFEST.in
+!README.md
+!HISTORY.rst
+!requirements*.txt
+!setup.py
+!setup.cfg
+!mypy.ini
+!pyproject.toml
+!conftest.py
+!uv.lock
+!docker-entrypoint.sh
+
+**/*.pyc
+**/*~

mockstack-0.7.1/.github/workflows/publish-to-dockerhub.yml

@@ -0,0 +1,53 @@
+name: Publish Docker image to DockerHub
+
+permissions:
+  contents: read
+  pull-requests: write
+
+on:
+  push:
+    branches:
+      - "**"
+    tags:
+      - "*.*.*"
+  pull_request:
+
+jobs:
+  docker:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          # list of Docker images to use as base name for tags
+          images: |
+            mockstack/mockstack
+          # generate Docker tags based on the following events/attributes
+          tags: |
+            type=ref,event=branch
+            type=ref,event=pr
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=semver,pattern={{major}}
+            type=sha
+
+      - name: Login to Docker Hub
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@v3
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Build and push
+        uses: docker/build-push-action@v6
+        with:
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}

mockstack-0.7.1/Dockerfile

@@ -0,0 +1,72 @@
+# ---------------------------- Build Time Arguments ----------------------------
+
+# Define build argument for version
+ARG PYTHON_IMAGE_VERSION=3.13.3-slim
+ARG MOCKSTACK_VERSION=0.1.0
+
+# ---------------------------- Base Image --------------------------------
+
+FROM python:${PYTHON_IMAGE_VERSION} AS base
+
+# Install system dependencies
+RUN apt-get update && apt-get install --no-install-recommends -y \
+    curl \
+    git \
+    && rm -rf /var/lib/apt/lists/*
+
+# Install uv and add it to PATH
+ENV PATH="/root/.local/bin:${PATH}"
+SHELL ["/bin/bash", "-o", "pipefail", "-c"]
+RUN curl -LsSf https://astral.sh/uv/install.sh | sh
+
+# ---------------------------- Builder --------------------------------
+
+FROM base AS builder
+
+ARG MOCKSTACK_VERSION
+
+# Maintainer label
+LABEL maintainer="mockstack.contact@gmail.com"
+
+# Set working directory
+WORKDIR /app
+
+# Create package structure
+RUN mkdir -p /app/src/mockstack /usr/local/share/mockstack/templates
+
+# Copy package files
+COPY mockstack /app/src/mockstack/
+COPY docker-entrypoint.sh pyproject.toml setup.* README.md /app/
+
+WORKDIR /app
+
+# Set version using build argument. Needs to happen before
+# we install the package with `pip install -e` below.
+ENV SETUPTOOLS_SCM_PRETEND_VERSION=${MOCKSTACK_VERSION}
+
+# Create and activate virtual environment, then install dependencies
+RUN uv venv && \
+    . .venv/bin/activate
+
+RUN uv pip install -e .
+
+# ---------------------------- Runner --------------------------------
+
+FROM builder AS runner
+
+# Set required environment variables for virtualenv
+ENV VIRTUAL_ENV="/app/.venv"
+ENV PATH="/app/.venv/bin:$PATH"
+
+# Set default
+ENV MOCKSTACK__TEMPLATES_DIR=/usr/local/share/mockstack/templates
+
+# Create a sample template file for default running of mockstack
+RUN echo '{"message": "Hello from mockstack!"}' > /usr/local/share/mockstack/templates/index.j2
+
+# Expose the default port
+EXPOSE 8000
+
+# Set the entrypoint to run the mockstack service
+ENTRYPOINT ["/app/docker-entrypoint.sh"]
+CMD ["uv", "run", "mockstack"]

{mockstack-0.6.1/mockstack.egg-info → mockstack-0.7.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mockstack
-Version: 0.6.1
+Version: 0.7.1
 Summary: An API mocking workhorse
 Author-email: Adam Ever-Hadani <mockstack.contact@gmail.com>
 License-Expression: MIT
@@ -37,6 +37,8 @@ Dynamic: license-file
 [![CI](https://github.com/adamhadani/mockstack/actions/workflows/ci.yml/badge.svg)](https://github.com/adamhadani/mockstack/actions/workflows/ci.yml)
 [![GitHub License](https://img.shields.io/github/license/adamhadani/mockstack)](https://github.com/adamhadani/mockstack/blob/main/LICENSE)
 [![PyPI - Version](https://img.shields.io/pypi/v/mockstack)](https://pypi.org/project/mockstack/)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/mockstack)](https://pypi.org/project/mockstack/)
+
 
 An API mocking workhorse :racehorse:
 
@@ -48,21 +50,21 @@ Use mockstack for:
 
 * **Integration Testing** :ok_hand:. Creating a consistent environment for running integration tests on a single component, using fixture responses.
 
-* **LLM-powered Workflows** :alien:. Speeding up development of LLM-based workflows and tools for use with frameworks such as [LangChain](https://python.langchain.com/docs/introduction/), [LangGraph](https://www.langchain.com/langgraph) and others. When developing LLM-driven execution graphs, you often want to have a consistent response from a tool while you're tuning prompts or debugging other aspects of a particular trace. `mockstack` can give you a solid foundation for this.
+* **LLM-powered Workflows** :alien:. Speeding up development of LLM-based workflows and tools for use with frameworks such as [LangChain](https://python.langchain.com/docs/introduction/), [LangGraph](https://www.langchain.com/langgraph) and others. When developing LLM-driven execution graphs, you often want to have a consistent response from a tool while you're tuning prompts or debugging other aspects of a particular trace. **mockstack** can give you a solid foundation for this.
 
-* **Chaos Engineering** :boom:. mockstack can simulate various real-world runtime error scenarios such as timeouts, http error codes, and invalid response payloads. This can be a great way to do some upfront "chaos monkey" type of testing on software components.
+* **Chaos Engineering** :boom:. mockstack can simulate various real-world runtime error scenarios such as timeouts, http error codes, and invalid response payloads. This can be a great way to do some upfront [Chaos Monkey](https://github.com/Netflix/chaosmonkey) type of testing on software components.
 
 Highlights include:
 
-* Multiple strategies for handling requests such as Jinja2 template files with intelligent URL request-to-template routing, proxy strategy, and mixed strategies. :game_die:
-* Observability via OpenTelemetry integration. Get detailed traces of your sessions instantly reported to backends such as Grafana, Jaeger, Zipkin, etc. :eyes:
-* Configurability via `pydantic-settings` supports customizing behaviour via environment variables and a `.env` file. :flags:
+* Multiple strategies for handling requests such as [Jinja](https://jinja.palletsprojects.com/en/stable/) template files with intelligent URL request-to-template routing, proxy strategy, and mixed strategies. :game_die:
+* Observability via [OpenTelemetry](https://opentelemetry.io/) integration. Get detailed traces of your sessions instantly reported to backends such as [Grafana](https://grafana.com/), [Jaeger](https://www.jaegertracing.io/), [Zipkin](https://zipkin.io/), etc. :eyes:
+* Configurability via [pydantic-settings](https://docs.pydantic.dev/latest/concepts/pydantic_settings/) supports customizing behaviour via environment variables and a `.env` file. :flags:
 * Comprehensive unit-tests, linting and formatting coverage as well as vulnerabilities and security scanning with full CI automation to ensure stability and a high-quality codebase for production-grade use. :+1:
 
 
 ## Installation
 
-Install using [uv](https://docs.astral.sh/uv/). This package conforms the concept of a [tool](https://docs.astral.sh/uv/concepts/tools/) and hence can simply install / run with `uvx`:
+Install using [uv](https://docs.astral.sh/uv/). This package conforms the concept of a [tool](https://docs.astral.sh/uv/concepts/tools/) and hence can simply install / run with [uvx](https://docs.astral.sh/uv/guides/tools/):
 
     uvx mockstack --help
 

{mockstack-0.6.1 → mockstack-0.7.1}/README.md

@@ -6,6 +6,8 @@
 [![CI](https://github.com/adamhadani/mockstack/actions/workflows/ci.yml/badge.svg)](https://github.com/adamhadani/mockstack/actions/workflows/ci.yml)
 [![GitHub License](https://img.shields.io/github/license/adamhadani/mockstack)](https://github.com/adamhadani/mockstack/blob/main/LICENSE)
 [![PyPI - Version](https://img.shields.io/pypi/v/mockstack)](https://pypi.org/project/mockstack/)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/mockstack)](https://pypi.org/project/mockstack/)
+
 
 An API mocking workhorse :racehorse:
 
@@ -17,21 +19,21 @@ Use mockstack for:
 
 * **Integration Testing** :ok_hand:. Creating a consistent environment for running integration tests on a single component, using fixture responses.
 
-* **LLM-powered Workflows** :alien:. Speeding up development of LLM-based workflows and tools for use with frameworks such as [LangChain](https://python.langchain.com/docs/introduction/), [LangGraph](https://www.langchain.com/langgraph) and others. When developing LLM-driven execution graphs, you often want to have a consistent response from a tool while you're tuning prompts or debugging other aspects of a particular trace. `mockstack` can give you a solid foundation for this.
+* **LLM-powered Workflows** :alien:. Speeding up development of LLM-based workflows and tools for use with frameworks such as [LangChain](https://python.langchain.com/docs/introduction/), [LangGraph](https://www.langchain.com/langgraph) and others. When developing LLM-driven execution graphs, you often want to have a consistent response from a tool while you're tuning prompts or debugging other aspects of a particular trace. **mockstack** can give you a solid foundation for this.
 
-* **Chaos Engineering** :boom:. mockstack can simulate various real-world runtime error scenarios such as timeouts, http error codes, and invalid response payloads. This can be a great way to do some upfront "chaos monkey" type of testing on software components.
+* **Chaos Engineering** :boom:. mockstack can simulate various real-world runtime error scenarios such as timeouts, http error codes, and invalid response payloads. This can be a great way to do some upfront [Chaos Monkey](https://github.com/Netflix/chaosmonkey) type of testing on software components.
 
 Highlights include:
 
-* Multiple strategies for handling requests such as Jinja2 template files with intelligent URL request-to-template routing, proxy strategy, and mixed strategies. :game_die:
-* Observability via OpenTelemetry integration. Get detailed traces of your sessions instantly reported to backends such as Grafana, Jaeger, Zipkin, etc. :eyes:
-* Configurability via `pydantic-settings` supports customizing behaviour via environment variables and a `.env` file. :flags:
+* Multiple strategies for handling requests such as [Jinja](https://jinja.palletsprojects.com/en/stable/) template files with intelligent URL request-to-template routing, proxy strategy, and mixed strategies. :game_die:
+* Observability via [OpenTelemetry](https://opentelemetry.io/) integration. Get detailed traces of your sessions instantly reported to backends such as [Grafana](https://grafana.com/), [Jaeger](https://www.jaegertracing.io/), [Zipkin](https://zipkin.io/), etc. :eyes:
+* Configurability via [pydantic-settings](https://docs.pydantic.dev/latest/concepts/pydantic_settings/) supports customizing behaviour via environment variables and a `.env` file. :flags:
 * Comprehensive unit-tests, linting and formatting coverage as well as vulnerabilities and security scanning with full CI automation to ensure stability and a high-quality codebase for production-grade use. :+1:
 
 
 ## Installation
 
-Install using [uv](https://docs.astral.sh/uv/). This package conforms the concept of a [tool](https://docs.astral.sh/uv/concepts/tools/) and hence can simply install / run with `uvx`:
+Install using [uv](https://docs.astral.sh/uv/). This package conforms the concept of a [tool](https://docs.astral.sh/uv/concepts/tools/) and hence can simply install / run with [uvx](https://docs.astral.sh/uv/guides/tools/):
 
     uvx mockstack --help
 

mockstack-0.7.1/docker-entrypoint.sh

@@ -0,0 +1,8 @@
+#!/bin/bash
+
+# Any setup commands can go here
+# For example:
+# python -m alembic upgrade head
+
+# Then run the command passed to the container
+exec "$@"

{mockstack-0.6.1 → mockstack-0.7.1}/examples/llm/mockstack-langchain-example.ipynb

@@ -42,7 +42,7 @@
   },
   {
    "cell_type": "code",
-   "execution_count": 31,
+   "execution_count": 38,
    "metadata": {},
    "outputs": [],
    "source": [
@@ -71,6 +71,51 @@
     "assert ai_msg.content == \"Hello! How can I assist you today?\""
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "Below is an identical example, but using OpenAI via Microsoft Azure.\n",
+    "\n",
+    "The only difference is that under the hood `LangChain` will hit an API URL of the form `/openai/v1/deployments/gpt-4o/chat/completions?api-version=<api-version>`.\n",
+    "\n",
+    "We can again handle this easily using templates by just creating a file with the name `openai-v1-deployments-gpt-4o-chat-completions.j2`.\n",
+    "\n",
+    "Remember you can also create conditional logic inside that file using Jinja syntax to return different mock responses depending on the request parameters, for instance using the query parameter `api-version`."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": 40,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from langchain_openai import AzureChatOpenAI\n",
+    "\n",
+    "\n",
+    "llm = AzureChatOpenAI(\n",
+    "    model=\"gpt-4o\",\n",
+    "    api_version=\"2024-02-15-preview\",\n",
+    "    temperature=0,\n",
+    "    max_tokens=None,\n",
+    "    timeout=None,\n",
+    "    max_retries=2,\n",
+    "    base_url=\"http://localhost:8000/openai/v1\",\n",
+    "    api_key=\"SOME_STRING_THAT_DOES_NOT_MATTER\",\n",
+    ")\n",
+    "\n",
+    "messages = [\n",
+    "    (\n",
+    "        \"system\",\n",
+    "        \"You are a helpful assistant that translates English to French. Translate the user sentence.\",\n",
+    "    ),\n",
+    "    (\"human\", \"I love programming.\"),\n",
+    "]\n",
+    "ai_msg = llm.invoke(messages)\n",
+    "\n",
+    "assert ai_msg.content == \"Hello! How can I assist you today?\""
+   ]
+  },
   {
    "cell_type": "markdown",
    "metadata": {},

mockstack-0.7.1/examples/llm/templates/openai-v1-deployments-gpt-4o-chat-completions.j2

@@ -0,0 +1,35 @@
+{
+  "id": "chatcmpl-B9MBs8CjcvOU2jLn4n570S5qMJKcT",
+  "object": "chat.completion",
+  "created": 1741569952,
+  "model": "gpt-4.1-2025-04-14",
+  "choices": [
+    {
+      "index": 0,
+      "message": {
+        "role": "assistant",
+        "content": "Hello! How can I assist you today?",
+        "refusal": null,
+        "annotations": []
+      },
+      "logprobs": null,
+      "finish_reason": "stop"
+    }
+  ],
+  "usage": {
+    "prompt_tokens": 19,
+    "completion_tokens": 10,
+    "total_tokens": 29,
+    "prompt_tokens_details": {
+      "cached_tokens": 0,
+      "audio_tokens": 0
+    },
+    "completion_tokens_details": {
+      "reasoning_tokens": 0,
+      "audio_tokens": 0,
+      "accepted_prediction_tokens": 0,
+      "rejected_prediction_tokens": 0
+    }
+  },
+  "service_tier": "default"
+}

{mockstack-0.6.1 → mockstack-0.7.1}/mockstack/display.py

@@ -1,6 +1,7 @@
 """Display and logging functionality."""
 
 import logging
+from importlib import metadata
 
 from fastapi import FastAPI
 
@@ -12,8 +13,10 @@ def announce(app: FastAPI, settings: Settings):
     logger = logging.getLogger("uvicorn")
     extra = {"markup": True}
 
+    version = metadata.version("mockstack")
+
     logger.info(
-        f"[bold medium_purple]mockstack[/bold medium_purple] ready to roll. "
+        f"[bold medium_purple]mockstack[/bold medium_purple] ready to roll. version: [medium_purple]{version}[/medium_purple]. "
         f"debug: [medium_purple]{settings.debug}[/medium_purple]. "
         f"strategy: [medium_purple]{settings.strategy}[/medium_purple]. ",
         extra=extra,

{mockstack-0.6.1 → mockstack-0.7.1/mockstack.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mockstack
-Version: 0.6.1
+Version: 0.7.1
 Summary: An API mocking workhorse
 Author-email: Adam Ever-Hadani <mockstack.contact@gmail.com>
 License-Expression: MIT
@@ -37,6 +37,8 @@ Dynamic: license-file
 [![CI](https://github.com/adamhadani/mockstack/actions/workflows/ci.yml/badge.svg)](https://github.com/adamhadani/mockstack/actions/workflows/ci.yml)
 [![GitHub License](https://img.shields.io/github/license/adamhadani/mockstack)](https://github.com/adamhadani/mockstack/blob/main/LICENSE)
 [![PyPI - Version](https://img.shields.io/pypi/v/mockstack)](https://pypi.org/project/mockstack/)
+[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/mockstack)](https://pypi.org/project/mockstack/)
+
 
 An API mocking workhorse :racehorse:
 
@@ -48,21 +50,21 @@ Use mockstack for:
 
 * **Integration Testing** :ok_hand:. Creating a consistent environment for running integration tests on a single component, using fixture responses.
 
-* **LLM-powered Workflows** :alien:. Speeding up development of LLM-based workflows and tools for use with frameworks such as [LangChain](https://python.langchain.com/docs/introduction/), [LangGraph](https://www.langchain.com/langgraph) and others. When developing LLM-driven execution graphs, you often want to have a consistent response from a tool while you're tuning prompts or debugging other aspects of a particular trace. `mockstack` can give you a solid foundation for this.
+* **LLM-powered Workflows** :alien:. Speeding up development of LLM-based workflows and tools for use with frameworks such as [LangChain](https://python.langchain.com/docs/introduction/), [LangGraph](https://www.langchain.com/langgraph) and others. When developing LLM-driven execution graphs, you often want to have a consistent response from a tool while you're tuning prompts or debugging other aspects of a particular trace. **mockstack** can give you a solid foundation for this.
 
-* **Chaos Engineering** :boom:. mockstack can simulate various real-world runtime error scenarios such as timeouts, http error codes, and invalid response payloads. This can be a great way to do some upfront "chaos monkey" type of testing on software components.
+* **Chaos Engineering** :boom:. mockstack can simulate various real-world runtime error scenarios such as timeouts, http error codes, and invalid response payloads. This can be a great way to do some upfront [Chaos Monkey](https://github.com/Netflix/chaosmonkey) type of testing on software components.
 
 Highlights include:
 
-* Multiple strategies for handling requests such as Jinja2 template files with intelligent URL request-to-template routing, proxy strategy, and mixed strategies. :game_die:
-* Observability via OpenTelemetry integration. Get detailed traces of your sessions instantly reported to backends such as Grafana, Jaeger, Zipkin, etc. :eyes:
-* Configurability via `pydantic-settings` supports customizing behaviour via environment variables and a `.env` file. :flags:
+* Multiple strategies for handling requests such as [Jinja](https://jinja.palletsprojects.com/en/stable/) template files with intelligent URL request-to-template routing, proxy strategy, and mixed strategies. :game_die:
+* Observability via [OpenTelemetry](https://opentelemetry.io/) integration. Get detailed traces of your sessions instantly reported to backends such as [Grafana](https://grafana.com/), [Jaeger](https://www.jaegertracing.io/), [Zipkin](https://zipkin.io/), etc. :eyes:
+* Configurability via [pydantic-settings](https://docs.pydantic.dev/latest/concepts/pydantic_settings/) supports customizing behaviour via environment variables and a `.env` file. :flags:
 * Comprehensive unit-tests, linting and formatting coverage as well as vulnerabilities and security scanning with full CI automation to ensure stability and a high-quality codebase for production-grade use. :+1:
 
 
 ## Installation
 
-Install using [uv](https://docs.astral.sh/uv/). This package conforms the concept of a [tool](https://docs.astral.sh/uv/concepts/tools/) and hence can simply install / run with `uvx`:
+Install using [uv](https://docs.astral.sh/uv/). This package conforms the concept of a [tool](https://docs.astral.sh/uv/concepts/tools/) and hence can simply install / run with [uvx](https://docs.astral.sh/uv/guides/tools/):
 
     uvx mockstack --help
 

{mockstack-0.6.1 → mockstack-0.7.1}/mockstack.egg-info/SOURCES.txt

@@ -1,15 +1,19 @@
+.dockerignore
 .env.example
 .gitignore
 .pre-commit-config.yaml
 CODE_OF_CONDUCT.md
+Dockerfile
 LICENSE
 README.md
 SECURITY.md
+docker-entrypoint.sh
 mkdocs.yml
 pyproject.toml
 uv.lock
 .github/workflows/ci.yml
 .github/workflows/publish-docs.yml
+.github/workflows/publish-to-dockerhub.yml
 .github/workflows/publish-to-pypi.yml
 docs/configuration.md
 docs/assets/favicon.ico
@@ -25,6 +29,7 @@ examples/filefixtures-with-templates/templates/servicename2-api-v2-user.533ec889
 examples/llm/README.md
 examples/llm/mockstack-langchain-example.ipynb
 examples/llm/templates/openai-v1-chat-completions.j2
+examples/llm/templates/openai-v1-deployments-gpt-4o-chat-completions.j2
 examples/proxyrules-with-rules-file/.env.example
 examples/proxyrules-with-rules-file/README.md
 examples/proxyrules-with-rules-file/rules.yml