Adding Microsoft.DependencyMap API public preview versions

[KarthikK123]

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).
• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR is awaiting ARM reviewer feedback (label: WaitForARMFeedback).
  To learn when this PR will get reviewed, see ARM review queue at aka.ms/azsdk/pr-arm-review
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ The required check named TypeSpec Validation has failed. 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

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
TypeSpec	DependencyMap.Management	https://apiview.dev/Assemblies/Review/e749f410e0d94897aaeafdc54b986ba5?revisionId=d855ff2df8944e3c924f4746d9702334

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

Microsoft.DependencyMap

[gary-x-li]

Please fix the TypeSpec Validation and LintDiff errors first.

Also, please make sure to through OpenAPI specs PR creation guidance and follow the instructions there. Are you introducing brand new APIs, or are you adding a new version based on a previous version? It's hard to tell what are new for this PR.

[KarthikK123]

Please fix the TypeSpec Validation and LintDiff errors first.

Also, please make sure to through OpenAPI specs PR creation guidance and follow the instructions there. Are you introducing brand new APIs, or are you adding a new version based on a previous version? It's hard to tell what are new for this PR.

We have an API version which is in private preview. We are introducing a new version which is essentially the same as the previous one, but will be used for public preview without a feature flag. I have removed the private preview version from the PR, that is already merged into RPSaaSMaster branch in the private repo. This PR now only contains the new version

[mentat9]

Please fix the TypeSpec Validation and LintDiff errors first.
Also, please make sure to through OpenAPI specs PR creation guidance and follow the instructions there. Are you introducing brand new APIs, or are you adding a new version based on a previous version? It's hard to tell what are new for this PR.

We have an API version which is in private preview. We are introducing a new version which is essentially the same as the previous one, but will be used for public preview without a feature flag. I have removed the private preview version from the PR, that is already merged into RPSaaSMaster branch in the private repo. This PR now only contains the new version

Presumably your specs in the private REST repo have already been reviewed and signed off by ARM (IOW, the PR that added them has the ARMSignedOff label). If so, then please move your APIs to the public repo unchanged in one PR (include a comment with a link back to the ARMSignedOff PR in the private repo) and then make a separate PR for adding the new API.

Or if you prefer, add the new API version in the private repo first, get signoff and merge, then move it to the public repo in a new PR. Either way, when you move APIs across, don't make any changes, and always include a comment explaining what you are doing, including a link back to the previous PR in which that API version was reviewed and signed off by ARM.

[KarthikK123]

Please fix the TypeSpec Validation and LintDiff errors first.
Also, please make sure to through OpenAPI specs PR creation guidance and follow the instructions there. Are you introducing brand new APIs, or are you adding a new version based on a previous version? It's hard to tell what are new for this PR.

We have an API version which is in private preview. We are introducing a new version which is essentially the same as the previous one, but will be used for public preview without a feature flag. I have removed the private preview version from the PR, that is already merged into RPSaaSMaster branch in the private repo. This PR now only contains the new version

Presumably your specs in the private REST repo have already been reviewed and signed off by ARM (IOW, the PR that added them has the ARMSignedOff label). If so, then please move your APIs to the public repo unchanged in one PR (include a comment with a link back to the ARMSignedOff PR in the private repo) and then make a separate PR for adding the new API.

Or if you prefer, add the new API version in the private repo first, get signoff and merge, then move it to the public repo in a new PR. Either way, when you move APIs across, don't make any changes, and always include a comment explaining what you are doing, including a link back to the previous PR in which that API version was reviewed and signed off by ARM.

Understood, thanks. I'll close this PR and raise a new one once the PR is approved and merged in the private repository