[CHORE]: Move cedarpolicyplugin to plugins/external/cedar

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
65/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Compare plugins/external/cedar/ in IBM/mcp-context-forge with the target repository, then inspect the copied pyproject.toml and README.md. Run pip install -e plugins/external/cedar and pytest plugins/external/cedar/tests/; done means the plugin is present, installable, documented at its new home, and covered by CI lint and tests.

Written by the indexing model from the issue text.

Description

Summary

Move the cedarpolicyplugin external plugin from the mcp-context-forge monorepo into this repository at plugins/external/cedar/, as part of the broader plugin ecosystem separation tracked in IBM/mcp-context-forge#2100.

What to move

Copy the contents of plugins/external/cedar/ from IBM/mcp-context-forge verbatim:

plugins/external/cedar/
├── .dockerignore
├── .env.template
├── .ruff.toml
├── Containerfile
├── MANIFEST.in
├── Makefile
├── README.md
├── cedarpolicyplugin/
│   ├── __init__.py
│   ├── plugin-manifest.yaml
│   ├── plugin.py
│   └── schema.py
├── examples/
├── pyproject.toml
├── resources/
├── run-server.sh
└── tests/

Dependencies (as-is)

From pyproject.toml:

cedarpy>=4.8.7
mcp>=1.28.1,<2
mcp-contextforge-gateway>=1.0.8

The plugin is moved as-is. Version constraint updates and dependency review are tracked separately (see sub-issues).

Acceptance criteria

  • Plugin lands at plugins/external/cedar/ in this repository
  • pyproject.toml is present and installable (pip install -e plugins/external/cedar)
  • Existing tests pass (pytest plugins/external/cedar/tests/)
  • CI covers the plugin (lint + test)
  • README updated to reflect new home

References

Dominant language
Python
Stars
1
Forks
1
Avg merge
4h 29m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IBM/contextforge-examples

All issues in IBM/contextforge-examples

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.