Private endpoints and JEDI controllers

[pajind]

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Please ensure to add changelog with this PR by answering the following questions.

1. What's the purpose of the update?
   • new service onboarding
   • new API version
   • update existing version for new feature
   • update existing version to fix swagger quality issue in s360
   • Other, please clarify
2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
   • SDK of .NET (need service team to ensure code readiness)
   • SDK of Python
   • SDK of Java
   • SDK of Js
   • SDK of Go
   • PowerShell
   • CLI
   • Terraform
   • No, no need to refresh for updates in this PR

Contribution checklist:

• I commit to follow the Breaking Change Policy of "no breaking changes"
• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

• Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

  • Adding new API(s)
  • Adding a new API version
  • Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
  • Adding a new service

• Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

• If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

• Removing API(s) in stable version
• Removing properties in stable version
• Removing API version(s) in stable version
• Updating API in stable or public preview version with Breaking Change Validation errors
• Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

[majastrz]

Signed off from ARM side.

[pajind]

@jianyexi Can you please check and merge the PR. I got ARM sign off

[pajind]

@jianyexi Can you please check and merge. Its a blocker for our JEDI deadlines

[jianyexi]

@pajind could you fix the lint errors https://github.com/Azure/azure-rest-api-specs/pull/14776/checks?check_run_id=3542878612 ?
Why the model or property name start with capital character

[pajind]

@pajind could you fix the lint errors https://github.com/Azure/azure-rest-api-specs/pull/14776/checks?check_run_id=3542878612 ?
Why the model or property name start with capital character

@jianyexi These Lintdiff errors are for existing apis and were not there in earlier reviews. The service is years old. I can take all these errors/breaking changes including camelcase in next api version while increasing api version. This api version is already public

[jianyexi]

@pajind

        Pallavi Jindal
        FTE could you fix the lint errors https://github.com/Azure/azure-rest-api-specs/pull/14776/checks?check_run_id=3542878612 ?

Why the model or property name start with capital character

@jianyexi Jianye Xi FTE These Lintdiff errors are for existing apis and were not there in earlier reviews. The service is years old. I can take all these errors/breaking changes including camelcase in next api version while increasing api version. This api version is already public

Okay, I approved it ,as it's not newly introduced errors.

[jianyexi]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mikhailshilkov]

This looks wrong to me. Now, there's no way to tell what the shape of the eventual response is going to be. I believe all other resources declare their final response, even if in practice it's a long running operation, similarly to what the previous version did.

[msyyc]

/azp run