itential-mcp 0.1.0__tar.gz

itential_mcp-0.1.0/.github/workflows/premerge.yaml

@@ -0,0 +1,30 @@
+# .github/workflows/premerge.yml
+---
+name: Run pre merge pipeline
+
+on:
+  pull_request:
+    branches:
+      - devel
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.x'  # You can specify an exact version like '3.11'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Install the project
+        run: uv sync --all-extras --dev
+
+      - name: Run the permerge target
+        run: make premerge

itential_mcp-0.1.0/.github/workflows/release.yaml

@@ -0,0 +1,45 @@
+# .github/workflows/release.yml
+# This workflow will create a new release and upload it to PyPI.  It will run
+# whenever a new tag is merged into the repository.  It builds the application
+# and pushes it to PyPI.
+---
+name: Deploy package to PyPI
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+permissions:
+  contents: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+
+      - name: Install the project
+        run: uv sync --all-extras --dev
+
+      - name: Install tools
+        run: uv run pip install build twine
+
+      - name: Build package
+        run: uv run python -m build
+
+      - name: Publish to PyPI or TestPyPI
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
+        run: |
+            echo "Publishing to PyPI..."
+            twine upload dist/*

itential_mcp-0.1.0/.gitignore

@@ -0,0 +1,19 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+coverage.*
+htmlcov/
+.pytest_cache/
+.coverage
+
+# Virtual environments
+.venv
+
+# dotenv 
+.env
+
+

itential_mcp-0.1.0/.python-version

@@ -0,0 +1 @@
+3.10

itential_mcp-0.1.0/CODEOWNERS

@@ -0,0 +1,2 @@
+# Global owners for the whole repository
+* @itential/mcp-committers

itential_mcp-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,56 @@
+# Open Source Code of Conduct
+
+## Purpose
+
+This Code of Conduct sets expectations for behavior in our open source community. It ensures a respectful, safe, and inclusive environment for contributors, maintainers, users, and newcomers—regardless of background, skill level, or personal identity.
+
+Open source thrives when everyone can contribute without harassment, discrimination, or toxicity. If you're here to collaborate, you're expected to follow this.
+
+## Expected Behavior
+
+We expect all contributors to:
+
+- **Be respectful**: Value different perspectives. Disagree without personal attacks.
+- **Be constructive**: Critique code and ideas, not people. If something’s broken, propose a fix.
+- **Be inclusive**: Welcome beginners, mentor others, and use inclusive language.
+- **Take responsibility**: Own your mistakes, learn from feedback, and help improve the project.
+- **Communicate clearly**: Write good issues, PRs, and commit messages. Default to transparency.
+
+## Unacceptable Behavior
+
+These are **not tolerated**:
+
+- Hate speech, slurs, or discriminatory jokes.
+- Harassment, intimidation, or sustained disruption.
+- Doxxing or sharing private information without consent.
+- Trolling, flame wars, or intentionally derailing conversations.
+- “Gatekeeping” or belittling others based on experience, tools, or tech stack.
+
+## Enforcement
+
+Violations will be handled promptly and decisively:
+
+- Minor incidents may result in a warning.
+- Repeated or severe behavior can lead to bans from the project (GitHub issues, PRs, Slack/Discord, etc.).
+- Reports will be reviewed by the maintainers or a designated moderation team.
+
+## Reporting
+
+If you experience or witness a violation, **speak up**:
+
+- Email: opensource@itential.com
+- Or DM a maintainer in private on our official chat
+
+All reports are confidential. Retaliation against reporters **will not be tolerated**.
+
+## Scope
+
+This Code of Conduct applies in all project spaces, including:
+
+- GitHub issues and PRs
+- Community forums, chats, and meetings
+- Social media when representing the project
+
+## Attribution
+
+This code is based on the [Contributor Covenant](https://www.contributor-covenant.org), with pragmatic additions tailored for modern open source development.

itential_mcp-0.1.0/Containerfile

@@ -0,0 +1,40 @@
+# Copyright (c) 2025 Itential, Inc
+# GNU General Public License v3.0+ (see LICENSE or https://www.gnu.org/licenses/gpl-3.0.txt)
+
+# Create the builder container
+FROM ghcr.io/astral-sh/uv:python3.10-bookworm-slim AS builder
+
+# Install the project into `/app`
+WORKDIR /app
+
+# Enable bytecode compilation
+ENV UV_COMPILE_BYTECODE=1
+
+# Copy from the cache instead of linking since it's a mounted volume
+ENV UV_LINK_MODE=copy
+
+COPY pyproject.toml .
+COPY README.md .
+
+# Generate uv lock file
+RUN uv lock
+
+# Install the project's dependencies using the lockfile
+RUN uv sync --frozen --no-install-project --no-dev --no-editable
+
+# Then, add the rest of the project source code and install it
+ADD . /app
+RUN uv sync --frozen --no-dev --no-editable
+
+# Create the final container with the application installed
+FROM python:3.10-slim
+
+WORKDIR /app
+
+#COPY --from=builder --chown=app:app /app/.venv /app/.venv
+COPY --from=builder /app/.venv /app/.venv
+
+# Place executables in the environment at the front of the path
+ENV PATH="/app/.venv/bin:$PATH"
+
+ENTRYPOINT ["itential-mcp"]