Connector Source for previously certified EXPOCAD connector #722
Conversation
* Create IN-D KYC India * Delete IN-D KYC India * Create apiDefinition.swagger.json * Add files via upload * Create README.MD * Update README.MD * Delete README.MD * Delete apiDefinition.swagger.json * Delete apiProperties.json * Create IN-D Insurance * Delete IN-D Insurance * Create IN-D Insurance * Delete IN-D Insurance * Create Readme.md * Add files via upload * Add files via upload * Delete Readme.md * Delete apiDefinition.swagger.json * Delete apiProperties.json * Create Readme.md * Add files via upload * Add files via upload
There was a problem hiding this comment.
@mikefactorial The swagger is not up-to-date with the swagger you have provided in the certification portal. Please let us know if this is an update to your connector and you want to update your connector.
|
Hi @sriyen-msft. Thanks for the prompt response! This is an update, but also the first time this connector's source has been submitted to the repo since it was previously certified before the requirement for open sourcing. Following the instructions in the docs my assumption was we needed to submit the PR with the updates prior to submitting the updates to the connector via the ISV Studio. Let me know if we did something out of order. Thanks again! From the Docs: “Updates to certified connectors must first be made through a pull request to the dev branch for review by the connector owner. Once a pull request has been merged to the dev branch, the connector owner can submit the connector for certification through the Connector certification tab in ISV Studio. Once certified, the Microsoft Certification team will handle merging the updates from dev to master.” - https://github.com/Microsoft/PowerPlatformConnectors#contributing |
|
@sriyen-msft I've made the requested changes. I wasn't sure if I needed to rerequest your review after making the changes, but I did so if that was a mistake in protocol let me know so I don't do it again next time :) |
* Updating with latest API Definition JSON * Updating with latest API Definition and Properties * Updates / Fixes for paconn validate issues * Additional fixes for paconn validation * Updated formatting with new export * Fix for multiple x-ms-connector-metadata definitions * Updating readme with current list of operations * removing extra files and updates to readme.md * Read Me Updates for Prerequisite. * Updating icon brand color * Committing changes based on feedback from @sriyen-msft after initial PR #722 * Updated support website * Updated Response type * Removed extraneous folder Co-authored-by: Michael Ochs <mike@mikefactorial.com>
* Updating with latest API Definition JSON * Updating with latest API Definition and Properties * Updates / Fixes for paconn validate issues * Additional fixes for paconn validation * Updated formatting with new export * Fix for multiple x-ms-connector-metadata definitions * Updating readme with current list of operations * removing extra files and updates to readme.md * Read Me Updates for Prerequisite. * Updating icon brand color * Committing changes based on feedback from @sriyen-msft after initial PR microsoft#722 * Updated support website * Updated Response type * Removed extraneous folder Co-authored-by: Michael Ochs <mike@mikefactorial.com>
4 participants
This PR contains the source for a previously certified connector that was not open sourced at the time. There are several updates to the actions in this source as well including new actions related to finance as well as the required readme.md and metadata in the swagger json.
Please check the following conditions for your PR.
apiDefinition.swagger.jsonis validated usingpaconn validatecommand.apiProperties.jsonhas a valid brand color. Invalid brand colors are#007ee5and#ffffff.