microsoft / microsoft/PowerPlatformConnectors
[BUG] broken swagger json causing error in "Import from Github"
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Type of Connector
Custom Connector
Name of Connector
Import from github
Describe the bug
error :
Specified swagger has the following errors: 'Definition is not valid. Error: 'Error : paths/~1/securityDefinitions : The property 'securityDefinitions' is not valid. If this property is an extension, its name must begin with "x-". '
file: custom-connectors/MCP-Streamable-HTTP/apiDefinition.swagger.json
I believe this commit is the cause of this bug: Added success response
Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
- Click on New Custom Connector
- Choose Import from Github
- choose dev branch and connector as "MCP-streamable-http"
Expected behavior
Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with custom-connectors/MCP-Streamable-HTTP/apiDefinition.swagger.json and compare it with commit d0e166e18ee71275bb6a6f0561b66b3ddd6ef9d. Reproduce the Import from Github flow using the dev branch and MCP-streamable-http connector, then validate the corrected Swagger definition; done means the connector imports without the reported securityDefinitions error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100