Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polygon (Independent Publisher) #3641

Open
wants to merge 5 commits into
base: dev
Choose a base branch
from

Conversation

m-trifonov16
Copy link

@m-trifonov16 m-trifonov16 commented Sep 6, 2024


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.

@m-trifonov16 m-trifonov16 requested a review from a team as a code owner September 6, 2024 09:48
@vmanoharas
Copy link
Contributor

Hello @m-trifonov16

Kindly agree the CLA and follow below documents and submit your connector.

Settings.json and icon.png files are not required to submit.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip
https://github.com/microsoft/PowerPlatformConnectors/tree/dev/templates/Independent%20Publisher

@m-trifonov16
Copy link
Author

@m-trifonov16 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Itransition Group Ltd"

Copy link
Contributor

@vmanoharas vmanoharas left a comment

Choose a reason for hiding this comment

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

@m-trifonov16 m-trifonov16 changed the title Proposal - Polygon (Independent Publisher) Polygon (Independent Publisher) Sep 12, 2024
@m-trifonov16
Copy link
Author

image

image
image
image

@m-trifonov16
Copy link
Author

image

@m-trifonov16
Copy link
Author

m-trifonov16 commented Sep 13, 2024

Hello @vmanoharas, I've followed all the steps in the documentation, but I am facing some confusion regarding the artifacts. I created the package and generated the SAS URL, but it seems that I don't have the option to upload it to Partner Center. Here is the package for reference. Package

image

@vmanoharas
Copy link
Contributor

Hello @vmanoharas, I've followed all the steps in the documentation, but I am facing some confusion regarding the artifacts. I created the package and generated the SAS URL, but it seems that I don't have the option to upload it to Partner Center. Here is the package for reference. Package

image

Hi @m-trifonov16,

Partner Center is for Verified Publishers, for independent publishers the process is to submit it for review in GitHub. I will review your artifacts now.

Copy link
Contributor

@vmanoharas vmanoharas left a comment

Choose a reason for hiding this comment

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

Dear Partner

I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

@vmanoharas
Copy link
Contributor

[[certify-connector]]

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.

2 participants