Skip to content

Conversation

@tuxmailer-integration
Copy link
Contributor

@tuxmailer-integration tuxmailer-integration commented Mar 8, 2022


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.

Please note that we are experiencing a significant delay due to COVID delays, unanticipated team leaves, and high volume of connector submissions.

  • 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.

@tuxmailer-integration tuxmailer-integration requested a review from a team as a code owner March 8, 2022 06:10
@ghost
Copy link

ghost commented Mar 8, 2022

CLA assistant check
All CLA requirements met.

Copy link
Contributor Author

@tuxmailer-integration tuxmailer-integration left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TuxMailer (Non-Microsoft Publisher)

rahil1793
rahil1793 previously approved these changes Mar 8, 2022
Copy link
Contributor Author

@tuxmailer-integration tuxmailer-integration left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TuxMailer (Non-Microsoft Publisher)

Copy link
Contributor

@v-eisljami v-eisljami left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only include files necessary for the connector. The image include is not a part of the connector artifacts.

Copy link
Contributor

@v-eisljami v-eisljami left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove this image from the connector. This image isn't part of the connector and is not necessary, therefore is not needed, and it should be removed from the PR.

@v-eisljami v-eisljami merged commit 6a0557d into microsoft:dev Apr 8, 2022
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.

3 participants