-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
base: dev
Are you sure you want to change the base?
Conversation
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 |
@microsoft-github-policy-service agree company="Itransition Group Ltd" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @m-trifonov16,
Kindly remove the Proposal from the title and follow the below instruction to submit Independent publisher connector.
https://github.com/microsoft/PowerPlatformConnectors/tree/dev/templates/Independent%20Publisher
https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip
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 |
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. |
There was a problem hiding this 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.
[[certify-connector]] |
Hi @vmanoharas Thank you for your time and support. |
Hi @vmanoharas, I hope you’re doing well. I wanted to follow up on my previous message regarding the deployment status of our connector, could you please share any updates or a more precise timeline on when we might expect it to be available in the production environment? |
Hello @m-trifonov16, Apologies for the delay. Due to internal issues with the build pipeline, the certification process has been delayed. Please allow us this week to resolve it, and we will keep you updated. |
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.
apiDefinition.swagger.json
, by runningpaconn validate
command.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: