[Defender (RiskIQ) - EASM] Api version 2024-03-01-preview #28322

juyoung98 · 2024-03-19T17:28:59Z

Data Plane API - Pull Request

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

a private preview
a public preview
GA release

Change Scope

^{This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.}

Design Document:
Previous API Spec Doc: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/riskiq/data-plane/Microsoft.Easm/preview/2023-03-01-preview/easm.json
Updated paths:

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
Swagger-Suppression-Process
to get approval.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Helpful Links

Schedule a data plane REST API spec review

Checks stuck in `queued` state?

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.

fix #28855
fix #28855

openapi-pipeline-app · 2024-03-19T17:29:04Z

Next Steps to Merge

Next steps that must be taken to merge this PR:

❌ Your PR requires an API stewardship board review as it introduces a new API version (label: new-api-version). Schedule the review by following aka.ms/azsdk/onboarding/restapischedule.
❌ 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. In addition, refer to step 4 in the PR workflow diagram

openapi-pipeline-app · 2024-03-19T17:29:05Z

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]

There are no breaking changes.

Compared specs (v0.10.8)	new version	base version
easm.json	2024-03-01-preview(eec2d5b)	2023-03-01-preview(main)

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️⚠️LintDiff: 13 Warnings warning [Detail]

Compared specs (v2.2.2)	new version	base version
2024-03-01-preview	2024-03-01-preview(eec2d5b)	default(main)

[must fix]The following errors/warnings are introduced by current PR:

Rule	Message	Related RPC [For API reviewers]
⚠️ PaginationResponse	Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L240
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L250
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L351
⚠️ PaginationResponse	`value` property in pageable response should be required Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L379
⚠️ PaginationResponse	Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L407
⚠️ ListInOperationName	Since operation response has model definition in array type, it should be of the form '_list'. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L454
⚠️ OperationId	OperationId for get method on a collection should contain 'List' Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L455
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L506
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L933
⚠️ PaginationResponse	Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1110
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1827
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1873
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L7105

The following errors/warnings exist before current PR submission:

Only 30 items are listed, please refer to log for more details.

Rule	Message
⚠️ SecurityDefinitionDescription	Security definition should have a description. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L43
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L204
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L600
⚠️ PutRequestResponseScheme	A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'DataConnections_CreateOrReplaceDataConnection' Request Model: 'parameters[2].schema' Response Model: 'responses[200].schema' Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L634
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L644
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L696
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L837
⚠️ PutRequestResponseScheme	A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'DiscoveryGroups_CreateOrReplaceDiscoGroup' Request Model: 'parameters[2].schema' Response Model: 'responses[200].schema' Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L871
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L881
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L976
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1028
⚠️ PaginationResponse	`value` property in pageable response should be required Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1035
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1265
⚠️ PaginationResponse	Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1301
⚠️ PaginationResponse	Operation might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1434
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1542
⚠️ PutRequestResponseScheme	A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'SavedFilters_CreateOrReplaceSavedFilter' Request Model: 'parameters[2].schema' Response Model: 'responses[200].schema' Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1576
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1586
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1638
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1735
⚠️ PathParameterSchema	Path parameter should specify a maximum length (maxLength) and characters allowed (pattern). Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1781
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L1932
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2315
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2382
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2400
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2496
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2589
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2807
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L2975
⚠️ EnumInsteadOfBoolean	Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.Easm/preview/2024-03-01-preview/easm.json#L3131

️️✔️Avocado succeeded [Detail] [Expand]

Validation passes for Avocado.

️️✔️SwaggerAPIView succeeded [Detail] [Expand]

️️✔️TypeSpecAPIView succeeded [Detail] [Expand]

️️✔️ModelValidation succeeded [Detail] [Expand]

Validation passes for ModelValidation.

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️️✔️PoliCheck succeeded [Detail] [Expand]

Validation passed for PoliCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

️️✔️PR Summary succeeded [Detail] [Expand]

Validation passes for Summary.

️️✔️Automated merging requirements met succeeded [Detail] [Expand]

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2024-03-19T17:29:05Z

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

 Please click here to preview with your @microsoft account.

️❌ azure-sdk-for-net-track2 failed [Detail]

❌Failed in generating from d4c4688. SDK Automation 14.0.0

command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
warn		specification/riskiq/data-plane/readme.md skipped due to azure-sdk-for-net-track2 not found in swagger-to-sdk
command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/Invoke-GenerateAndBuildV2.ps1:131
cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
cmderr	[Invoke-GenerateAndBuildV2.ps1]  131 |                GeneratePackage `
cmderr	[Invoke-GenerateAndBuildV2.ps1]      |                ~~~~~~~~~~~~~~~~~
cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to build sdk. exit code: False
cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/Invoke-GenerateAndBuildV2.ps1:131
cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
cmderr	[Invoke-GenerateAndBuildV2.ps1]  131 |                GeneratePackage `
cmderr	[Invoke-GenerateAndBuildV2.ps1]      |                ~~~~~~~~~~~~~~~~~
cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to packe sdk. exit code: False
cmderr	[Invoke-GenerateAndBuildV2.ps1] Get-ChildItem: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/automation/GenerateAndBuildLib.ps1:807
cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
cmderr	[Invoke-GenerateAndBuildV2.ps1]  807 |  … rtifacts += Get-ChildItem $artifactsPath -Filter *.nupkg -exclude *.s …
cmderr	[Invoke-GenerateAndBuildV2.ps1]      |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Cannot find path
cmderr	[Invoke-GenerateAndBuildV2.ps1]      | '/mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/packages/Debug/' because
cmderr	[Invoke-GenerateAndBuildV2.ps1]      | it does not exist.
cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/Invoke-GenerateAndBuildV2.ps1:131
cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
cmderr	[Invoke-GenerateAndBuildV2.ps1]  131 |                GeneratePackage `
cmderr	[Invoke-GenerateAndBuildV2.ps1]      |                ~~~~~~~~~~~~~~~~~
cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to generate sdk artifact

❌Azure.Analytics.Defender.Easm [Preview SDK Changes]
```
info	[Changelog]
```

️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]

️✔️Succeeded in generating from d4c4688. SDK Automation 14.0.0

command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
warn		specification/riskiq/data-plane/readme.md skipped due to azure-sdk-for-js not found in swagger-to-sdk
command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json

️✔️@azure-rest/defender-easm-rest [Preview SDK Changes]

azure-rest-defender-easm-rest-1.0.0-beta.1.tgz

info	[Changelog]
error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.

️❌ azure-sdk-for-java failed [Detail]

❌Failed in generating from d4c4688. SDK Automation 14.0.0

command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
warn		specification/riskiq/data-plane/readme.md skipped due to azure-sdk-for-java not found in swagger-to-sdk
command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
cmderr	[generate.py] [COMPILE] Maven build fail.
cmderr	[generate.py] One reason of the compilation failure is that the existing code customization in SDK repository being incompatible with the class generated from updated TypeSpec source. In such case, you can ignore the failure, and fix the customization in SDK repository.
cmderr	[generate.py] You can inquire in "Language - Java" Teams channel. Please include the link of this Pull Request in the query.

❌azure-analytics-defender-easm [Preview SDK Changes]
- pom.xml

_{Posted by Swagger Pipeline | How to fix these errors?}

openapi-pipeline-app · 2024-03-19T17:29:06Z

Generated ApiView

Language	Package Name	ApiView Link
JavaScript	@azure-rest/defender-easm-rest	https://apiview.dev/Assemblies/Review/b21bc05136b840ef93025807dcaa483f?revisionId=fa8cbfd996e94e8891f03060d77e0c0a
Swagger	Microsoft.Easm	https://apiview.dev/Assemblies/Review/f342fa03d74e4fd59892676d74db996e?revisionId=6e70ed06c0e042f3b9b6e17fa6ac7cdb
TypeSpec	Easm	https://apiview.dev/Assemblies/Review/c2e5d55db3fa4ae9a05ae50da30092de?revisionId=e3bf0213d1a748d0b3085eba9e4c8dae

openapi-pipeline-app · 2024-03-21T16:54:41Z

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

weidongxu-microsoft

There seems to be major changes to the new api-version.

Make sure you had scheduled an API review meeting.

weidongxu-microsoft · 2024-04-24T01:14:18Z

specification/riskiq/Easm/main.tsp

-  @doc("Version 2023-03-01-preview")
+  #suppress "@azure-tools/typespec-azure-core/documentation-required" "Documentation will be added next preview version"


I don't see the reason why you replace a doc with a suppress?

this was a mistake. We will add it back. Thanks

weidongxu-microsoft · 2024-04-24T01:16:56Z

specification/riskiq/Easm/models.tsp

+@doc("A request body used to export an asset.")
+@Versioning.added(Versions.v2024_03_01_preview)
+model AssetsExportRequestBody {
+  #suppress "@azure-tools/typespec-azure-core/documentation-required" "Documentation will be added next preview version"


I don't think this "Documentation will be added next preview version" is a valid approach.

Please add them in THIS version. <-- you can wait after API review, but definitely before merge

juyoung98 · 2024-04-24T17:52:24Z

There seems to be major changes to the new api-version.

Make sure you had scheduled an API review meeting.

There are no breaking changes so this PR wasn't labeled that we need a review. We are only adding new endpoints, not making breaking changes. Do we still need a review? If so, why?

weidongxu-microsoft · 2024-04-26T01:51:43Z

There seems to be major changes to the new api-version.
Make sure you had scheduled an API review meeting.

There are no breaking changes so this PR wasn't labeled that we need a review. We are only adding new endpoints, not making breaking changes. Do we still need a review? If so, why?

https://eng.ms/docs/products/azure-developer-experience/design/api-review

johanste · 2024-05-02T23:12:24Z

specification/riskiq/Easm/models.tsp

+
+@doc("A request body used to retrieve a delta summary.")
+@Versioning.added(Versions.v2024_03_01_preview)
+model DeltaSummaryRequestBody {


Let's remove the "body" suffix. Is either value required? What happens if you provide neither?

openapi-pipeline-app · 2024-05-09T21:46:23Z

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

…required

openapi-pipeline-app · 2024-05-13T22:13:18Z

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

adding new and updated endpoints to azure review

0e3294c

juyoung98 requested a review from a team as a code owner March 19, 2024 17:29

juyoung98 requested review from weidongxu-microsoft and mikekistler and removed request for a team March 19, 2024 17:29

AzureRestAPISpecReview added data-plane TypeSpec Authored with TypeSpec labels Mar 19, 2024

update respective swagger file for version 2024-03-01

8b1f3a9

AzureRestAPISpecReview added new-api-version RPaaS labels Mar 19, 2024

Juyoung Song and others added 7 commits March 19, 2024 12:21

fixing Swagger pipeline check failures

153e977

conclude merge

9a8569c

update client file with new endpoints, small naming convention changes

536d69e

update the swagger file

53cd024

adding examples

eab140d

files didn't get added

de51f0a

fixing more checks

4e04b5b

juyoung98 and others added 5 commits March 21, 2024 10:05

Merge branch 'main' into riskiq/Microsoft.Easm/2024-03-01-preview

a389a63

fixing cspell format

16d58c0

fixing more checks

8115491

fixing more examples

34c2375

adding second set of examples

7f93ab6

weidongxu-microsoft mentioned this pull request Apr 24, 2024

Update azure-analytics-defender-easm module, reflect latest spec Azure/azure-sdk-for-java#39862

Open

weidongxu-microsoft reviewed Apr 24, 2024

View reviewed changes

adamgitazure added 2 commits April 24, 2024 15:53

add documentations for newly added models

bcc0116

try adding doc for the Versions enum

930d4d0

johanste reviewed May 2, 2024

View reviewed changes

add discogroup delete, modify aseetChian realted apis

17076a6

adamgitazure added 4 commits May 9, 2024 15:07

fix merge conflict

147ed25

correct examples for assetChain related endpoints

aed6ea3

dismissAssetChain should be resourceCollectionAction

a32117b

remove word body from request, update some property from optional to …

203b67f

…required

adamgitazure added 3 commits May 13, 2024 16:04

fix merge conflict

a57ac1d

add doc to enums

549bf7c

fix a typo and update dependecies using npm ci

eec2d5b

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Defender (RiskIQ) - EASM] Api version 2024-03-01-preview #28322

[Defender (RiskIQ) - EASM] Api version 2024-03-01-preview #28322

juyoung98 commented Mar 19, 2024 •

edited by azure-sdk

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 21, 2024

weidongxu-microsoft left a comment •

edited

weidongxu-microsoft Apr 24, 2024

juyoung98 Apr 24, 2024

weidongxu-microsoft Apr 24, 2024 •

edited

juyoung98 commented Apr 24, 2024

weidongxu-microsoft commented Apr 26, 2024

johanste May 2, 2024

openapi-pipeline-app bot commented May 9, 2024

openapi-pipeline-app bot commented May 13, 2024

		@doc("Version 2023-03-01-preview")
		#suppress "@azure-tools/typespec-azure-core/documentation-required" "Documentation will be added next preview version"

[Defender (RiskIQ) - EASM] Api version 2024-03-01-preview #28322

Are you sure you want to change the base?

[Defender (RiskIQ) - EASM] Api version 2024-03-01-preview #28322

Conversation

juyoung98 commented Mar 19, 2024 • edited by azure-sdk

Data Plane API - Pull Request

API Info: The Basics

Change Scope

Viewing API changes

Suppressing failures

❔Got questions? Need additional info?? We are here to help!

Tooling

Guidelines & Specifications

Helpful Links

openapi-pipeline-app bot commented Mar 19, 2024 • edited

Next Steps to Merge

openapi-pipeline-app bot commented Mar 19, 2024 • edited

Swagger Validation Report

openapi-pipeline-app bot commented Mar 19, 2024 • edited

Swagger Generation Artifacts

openapi-pipeline-app bot commented Mar 19, 2024 • edited

Generated ApiView

openapi-pipeline-app bot commented Mar 21, 2024

weidongxu-microsoft left a comment • edited

Choose a reason for hiding this comment

weidongxu-microsoft Apr 24, 2024

Choose a reason for hiding this comment

juyoung98 Apr 24, 2024

Choose a reason for hiding this comment

weidongxu-microsoft Apr 24, 2024 • edited

Choose a reason for hiding this comment

juyoung98 commented Apr 24, 2024

weidongxu-microsoft commented Apr 26, 2024

johanste May 2, 2024

Choose a reason for hiding this comment

openapi-pipeline-app bot commented May 9, 2024

openapi-pipeline-app bot commented May 13, 2024

juyoung98 commented Mar 19, 2024 •

edited by azure-sdk

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

openapi-pipeline-app bot commented Mar 19, 2024 •

edited

weidongxu-microsoft left a comment •

edited

weidongxu-microsoft Apr 24, 2024 •

edited