entrypoint: export PLANE_API_KEY alias from PLANE_TOKEN#7
Merged
Conversation
The m365-mcp wrapper scripts (and agent-config plane MCP) read PLANE_API_KEY; our ExternalSecret writes the value as PLANE_TOKEN per WOVED-36's naming convention. Bridge the two in the entrypoint so wrapper scripts work without each repo having to know about both names.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bridges naming gap between WOVED-36's PLANE_TOKEN convention and the m365-mcp scripts' PLANE_API_KEY expectation. Single line, ENV-only.