Skip to content

Conversation

@sankumrav
Copy link
Owner


When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

  • I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
  • Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
  • Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

sankumrav and others added 21 commits September 23, 2022 23:05
* Initial commit.

* Made changes to swagger and README

Co-authored-by: tarynsnell <tsnell@realdataconsulting.com>
* connector artifacts

initial commit of connector artifacts

* iconbrandcolor

replacing default color per pull request guidelines

* Swagger and Change Validation

updating swagger per issues identified in validation phase

* property names, values, grammar

updating per recent microsoft pull request notes around property names having proper casing, grammar, and correct values in the case of the privacy policy property.

* iconBrandColor

updating brand color
Add reusable parameter and issue fix in the api definition
* GitLab (Independent Publisher)

Added support triggering pipelines, creating a pipeline trigger, linking a runner to a project, and updating a merge request.

* GitLab (Independent Publisher)

Fixed swagger issues

* GitLab (Independent Publisher)

Updated summaries

* GitLab (Independent Publisher)

Removed warnings
* Add files via upload

* Update apiDefinition.swagger.json
* initial commit

* initial commit

* addresed the review comments.

* Add reusable parameter and issue fix in the api definition

* addresed the review comments.

* addresed the review comments.

* addresed the review comments.

* addresed the review comments.

Co-authored-by: Austin Wu <wuaustin@microsoft.com>
* Open Sourcing Connector files

* Address all comments by @v-EgorKozhadei
@sankumrav sankumrav merged commit 0a26952 into dev Sep 29, 2022
sankumrav pushed a commit that referenced this pull request Dec 9, 2022
* Encodian March 21 Release

* Encodian April 21 Release

* Encodian May 21 Release

* Encodian June 21 Release

* Encodian - June 21 Release #2

* Encodian - August Release #1

* Encodian - Nov 21 Release

* Encodian - Nov 21 Release #2

* Encodian March 22

* Encodian March 22 #2

* Encodian March 22 #3

* Encodian March 22 #4

* Encodian March 22 #5

* March 22 Release (Updated)

* Encodian Oct 22 Release

* Encodian October 22 Release #2

* Updates

* Minor update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants