updated accept mission custom connector

[kunj-sangani]

---

Updated the Accept Mission connector which is a certified connector as my team own those APIs

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

[vmanoharas]

Hi @kunj-sangani,

Please revert the changes in the schema file as well that you modified in this PR - https://github.com/microsoft/PowerPlatformConnectors/pull/4058/files#diff-426dee6e7364a3727c8c2adeec5a483bd2526b805234367a9f42457dc694bfe1

[kunj-sangani]

Hi @vmanoharas ,

Would it be Ok if I close that PR?
As I have lost access to that fork

[vmanoharas]

Hi @vmanoharas ,

Would it be Ok if I close that PR? As I have lost access to that fork

Hi @kunj-sangani,

Sure, you can close and revert the schema file changes in the PR or create a new PR.