Added version 2024-06-01-preview for Azure API Center resource manager API

[azaslonov]

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• New resource provider.
• New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
• Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
• Update existing version to fix OpenAPI spec quality issues in S360.
• Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
• Other, please clarify:
  • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• I have reviewed following Resource Provider guidelines, including
  ARM resource provider contract and
  REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This is the public specs repo main branch which is not intended for iterative development.
  You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
  If this is what you intend, add PublishToCustomers label to your PR.
  Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/apicenter/armapicenter	https://apiview.dev/Assemblies/Review/fe1f8ab2d7e042b0aa5311028b6a89f4?revisionId=2a69c4303e544ea29eea864ac0a61f8a
Python	azure-mgmt-apicenter	https://apiview.dev/Assemblies/Review/22c8c98c8fa34f6cae067455dd4e6bc3?revisionId=c35bddd104054b36b1e11bd4604c420c
Java	azure-resourcemanager-apicenter	https://apiview.dev/Assemblies/Review/c3d1b056c7ff4f94b6fbc5595604921d?revisionId=bfb8dd7a3c214e15bde3a5ac9eaf8b6e
JavaScript	@azure/arm-apicenter	https://apiview.dev/Assemblies/Review/d67bde3d58b441ca80a04c64ad755a6b?revisionId=ba644982055849f58196e6c81c7a7258
Swagger	Microsoft.ApiCenter	https://apiview.dev/Assemblies/Review/3c9fafea50ce44d9a36a97c2e9751516?revisionId=5e41827ea56a4dfbbf2051fd0c8b4d1b
TypeSpec	ApiCenter.Management	https://apiview.dev/Assemblies/Review/2f0836bbf6354d28a4643b2ec5e5f5e8?revisionId=4987ee04d5a3426790f9a81e04672144

[ramoka178]

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiCenter/services/{serviceName}/importFromApim": {

can it be more descriptive ? importFromApiManagement?

---

Refers to: specification/apicenter/resource-manager/Microsoft.ApiCenter/preview/2024-06-01-preview/apicenter.json:672 in e9b5fd5. [](commit_id = e9b5fd5, deletion_comment = False)

Removed it for now.

[ramoka178]

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiCenter/services/{serviceName}/workspaces/{workspaceName}/apiSources/{apiSourceName}": {

no patch API needed?

---

Refers to: specification/apicenter/resource-manager/Microsoft.ApiCenter/preview/2024-06-01-preview/apicenter.json:1445 in e9b5fd5. [](commit_id = e9b5fd5, deletion_comment = False)

Nope, no PATCH.

[azaslonov]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).