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

Doppler (Independent Publisher) #3205

Merged
merged 4 commits into from
Mar 4, 2024
Merged

Conversation

developer-farhan
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.

4 Unique Operations

Doppler-Retrieve Doppler-Update Doppler-Delete Doppler-List

Test Operation Section

After_validation_1 After_validation_2

Paconn Validation

Paconn Validation

Solution Checker Validation

Solution Checker Validation

@developer-farhan developer-farhan requested a review from a team as a code owner January 22, 2024 13:54
@developer-farhan
Copy link
Contributor Author

@microsoft-github-policy-service agree

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.

Hello @officialFlutterDeveloper,

Could you please resolve review comments?

…& moved x-ms-connector-metadata to the end
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.

Hello @officialFlutterDeveloper,

Can you please update the iconBrandColor?

@vmanoharas
Copy link
Contributor

vmanoharas commented Jan 25, 2024

Hello @officialFlutterDeveloper,

Can you please correct the path of files? it seems that there is an empty file added as "git"
image

Please refer this link for other Independent connectors - https://github.com/microsoft/PowerPlatformConnectors/pull/3209/files

@developer-farhan
Copy link
Contributor Author

developer-farhan commented Jan 25, 2024

@vmanoharas 'git' file has been deleted :)

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.

Hello @officialFlutterDeveloper
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]]

@developer-farhan
Copy link
Contributor Author

@vmanoharas it was my honor working with you and the team. This has motivated me to work harder and make more useful and development needed connectors.

@vmanoharas
Copy link
Contributor

@vmanoharas it was my honor working with you and the team. This has motivated me to work harder and make more useful and development needed connectors.

Thank you @officialFlutterDeveloper . Your dedication and motivation are inspiring, and I look forward to witnessing the continued impact of your hard work.

@developer-farhan
Copy link
Contributor Author

developer-farhan commented Feb 17, 2024

@vmanoharas I am reaching out to request an update on the status of my connector deployment

@vmanoharas
Copy link
Contributor

Hello @officialFlutterDeveloper,

Thank you very much for reaching out!

Your connector is deployed to South East Asia region, it will be completed to all regions by next week.

@developer-farhan
Copy link
Contributor Author

@vmanoharas Requesting update on the connector deployement as the label has not been updated & how long it will take for my connector to show up here. Thanks :)

@vmanoharas
Copy link
Contributor

Hello Partner,
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.

@vmanoharas vmanoharas merged commit 5315841 into microsoft:dev Mar 4, 2024
4 checks passed
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