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

Leap-AI (Independent Publisher) #2480

Merged
merged 8 commits into from
May 17, 2023
Merged

Conversation

sekharmalla
Copy link
Contributor


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.

image

@Amjed-Ayoub
Copy link
Contributor

Hello @sekharmalla,

Thank you so much for submitting this PR. May I ask you please to double check your connector files? this PR has 0 files.

Thank you so much.

@Amjed-Ayoub Amjed-Ayoub added independent-publisher-connector needs:partner-attention On Hold We are reviewing your connector with our management, until then your PR will be on hold. New For brand new connector submissions labels Mar 21, 2023
@sekharmalla sekharmalla requested a review from a team as a code owner March 22, 2023 00:27
Updated README.MD with original content
@sekharmalla
Copy link
Contributor Author

Hello @Amjed-Ayoub,

Thanks for contacting me, it is strange to know that there no files in this PR coz I can clearly see them in the files changed.

image

image

Thank You

@Amjed-Ayoub Amjed-Ayoub added Validation phase Connector is being validated by Microsoft. and removed On Hold We are reviewing your connector with our management, until then your PR will be on hold. labels Mar 24, 2023
Updated README.md as per Microsoft template
changes as follows:

- removed API name from the definition file.
- changed all operationid to camel case.
- updated all response description to success.
changes as follows:

- added stack owner
@Amjed-Ayoub
Copy link
Contributor

[[certify-connector]]

@Amjed-Ayoub
Copy link
Contributor

Hello @sekharmalla ,
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.

@Amjed-Ayoub Amjed-Ayoub added certification-in-progress and removed Validation phase Connector is being validated by Microsoft. needs:partner-attention labels May 3, 2023
@Amjed-Ayoub
Copy link
Contributor

Hello @sekharmalla ,
I hope you are doing well.
Your connector is in production deployment and queued up for the next deployment schedule. This process typically takes 3-4 weeks. Please note that the documentation for your connector will not be generated until the deployment process is in the final steps.
Please let us know if you have any questions.
Thank you very much for working with us.

Copy link
Contributor

@Amjed-Ayoub Amjed-Ayoub left a comment

Choose a reason for hiding this comment

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

Hello @sekharmalla ,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.

@Amjed-Ayoub Amjed-Ayoub merged commit e48005a into microsoft:dev May 17, 2023
@Amjed-Ayoub Amjed-Ayoub removed deployment-in-progress New For brand new connector submissions labels May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants