microsoft / microsoft/PowerPlatformConnectors
Partner Centre Package structure
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Description of Feature or Work Requested
Hi Team,
We are trying to submit an update to our certified custom connector. In the past we have provided the commit id for the latest changes in ISV Studio, however this has now been moved to partner centre and requires we provide an SAS link to a .zip file for our connector.
The issue we are experiencing is that the structure of the .zip file outlined in the official documentation does not seem to be accepted by Partner Centre.
There is also of inconsistencies in the documentation for example:
- sometimes the files are upper case and sometimes lowercase depending on where you look
- sometimes the file needs to contan a Packages.zip, other time its outlined a a Package.zip (notice the plural)
- the naming of the folders is different to what is exported from Power automate solutions
Has anyone had any luck with generating a packaged .zip file for ther connector and successfully submitted for review via the partner centre?
Target Date
We would like to publish the change before 19th July 2024
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 the linked official custom connector certification documentation and compare its package structure with the structure accepted by Partner Centre. Check the reported filename casing, Package.zip versus Packages.zip, and exported folder names. Done means the required .zip layout is confirmed and the documentation is made consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100