Skip to content

Conversation

@allandecastro
Copy link

@allandecastro allandecastro commented Jan 26, 2023


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.

@allandecastro allandecastro requested a review from a team as a code owner January 26, 2023 20:58
@allandecastro
Copy link
Author

@microsoft-github-policy-service agree

@troystaylor
Copy link
Contributor

@allandecastro Please review your readme. You need to replace the description:

Pappers

24 Pull Requests' goal is to encourage contribution to open source projects during December. The site suggests open projects, highlights tickets that are good for new contributors, provides guides for contributing and promotes good contributions submitted each day.

@allandecastro allandecastro marked this pull request as draft January 26, 2023 22:42
@Amjed-Ayoub
Copy link
Contributor

@allandecastro thank you so much for your new submission.
If you would like us to review your connector files, please remove the "Proposal" from the PR title.

Thank you so much.

@Amjed-Ayoub Amjed-Ayoub added independent-publisher-connector New For brand new connector submissions Proposal labels Jan 27, 2023
@Amjed-Ayoub
Copy link
Contributor

Hello @allandecastro ,

I hope you are doing well.

We would like to know the status of your connector. It has been in our repo since January 2023.
Please let us know how you would like to proceed.

Please do not hesitate to reach out if you have any questions as we are always happy to help.

Thank you very much.

@vmanoharas
Copy link
Contributor

Hello @allandecastro,

This PR is in proposal state from many months. I am closing this PR, kindly reopen/create new PR, if you have any progress.

@vmanoharas vmanoharas closed this May 21, 2024
@troystaylor
Copy link
Contributor

Hello @allandecastro, I don't know if you still need this connector, but I have now submitted it:
#3514

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

Labels

independent-publisher-connector New For brand new connector submissions Proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants