makeplane / makeplane/plane

Missing `services.pi.enable` and `plane_oauth` configurations in Community Edition helm chart

Open
#9,431 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Hi all,

I've been using Plane Community Edition since v0.12-dev and recently upgraded to v1.3.1. While exploring the latest docs, I came across a couple of configurations that seem to be referenced in the official documentation but don't appear to be available in the CE Helm chart.

Missing configurations

1. services.pi.enable (Plane AI Services)

The official documentation describes a services.pi.enable configuration to enable Plane AI services, but this key does not seem to exist in the plane-ce Helm chart values.

2. plane_oauth (MCP Server OAuth configuration)

The MCP server self-hosting documentation describes a plane_oauth configuration block for the plane-ce Helm chart. This key also appears to be absent from the CE chart, which makes it impossible to configure the Plane MCP server on a self-hosted Community Edition instance.

Would love any clarification on when these might be available for CE users, or if there are any workarounds in enabling these services in the meantime. Thanks!

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.

Research direction

Compare the Plane AI services and MCP server self-hosting documentation with the Community Edition Helm chart values, focusing on the missing services.pi.enable and plane_oauth keys. Verify whether the chart omits these configurations and determine whether the expected outcome is to add them or align the documentation; completion should leave the documented CE configuration path available and consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.