Skip to content

Azure Defender EASM Public Preview #36282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

Conversation

shadahmed-microsoft
Copy link

Description

The SDK for Defender EASM Public Preview

product documentation
introductory session ticket
Typespec PR: Azure/azure-rest-api-specs#24937
arcboard: Azure/azure-sdk#5062

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@joshfree joshfree added the Client This issue points to a problem in the data-plane of the library. label Aug 21, 2023
The examples below require a Microsoft Defender EASM Resource and a corresponding authorized client.

Example of initializing a client:
```java com.azure.resourcemanager.defendereasm.readme
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tags should not use com.azure.resourcemanager. resourcemanager is for management libraries only.

Comment on lines +86 to +89
## Troubleshooting

## Next steps

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two sections should not be empty.

<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-core</artifactId>
<version>1.41.0</version> <!-- {x-version-update;com.azure:azure-core;dependency} -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These dependencies should be updated to latest released versions.

<scope>test</scope>
</dependency>
</dependencies>
<build>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

build section should not be included here. It will be derived from the parent pom.

<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>

<groupId>com.azure</groupId>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Parent pom reference is missing. Please add the parent pom as shown here.

@@ -0,0 +1,13 @@
# Release History
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The directory name should match the artifact id. This should be in sdk/easm/azure-analytics-defender-easm/ directory.


/** The AlexaInfo model. */
@Immutable
public final class AlexaInfo {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change the type name to AlexaDetails.

<packaging>pom</packaging>
<version>1.0.0</version><!-- Need not change for every release-->

<modules>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should update the root pom too as this PR is adding a new directory in sdk/.

<version>1.0.0</version><!-- Need not change for every release-->

<modules>
<module>azure-analytics-defendereasm</module>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the module name should be azure-analytics-defender-easm.

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.azure</groupId>
<artifactId>azure-analytics-defendereasm</artifactId>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be named azure-easm-service

@weidongxu-microsoft
Copy link
Member

weidongxu-microsoft commented Sep 14, 2023

@shadahmed-microsoft

You can ref to the automated PR in your spec PR for guide on the changes (e.g. root pom, version_client.txt, tsp-location.yaml, etc.)
https://github.com/azure-sdk/azure-sdk-for-java/pull/6936/files

Do use the correct package name and namespace. https://github.com/Azure/azure-rest-api-specs/pull/24937/files#r1325291737

@thang-bit
Copy link
Member

thang-bit commented Sep 29, 2023

@weidongxu-microsoft @srnagar , shad is no longer working for Microsoft, so I'm taking over this PR this sprint. I'm currently not having the permissions to push to this PR. Is it possible for me to get permission to push my changes here? Or is it advised to clone the repo and create another PR to replace this PR instead?

Thank you

@srnagar
Copy link
Member

srnagar commented Sep 29, 2023

@thang-bit You should have permissions now. Can you please verify?

If this doesn't work, you should just create a new PR as the previous account may not be active and won't allow further updates to the PR.

@thang-bit
Copy link
Member

@srnagar, I wasn't able to push my updates to this PR, so I created this PR: #37034 instead

@srnagar
Copy link
Member

srnagar commented Oct 3, 2023

Closing this PR in favor of #37034

@srnagar srnagar closed this Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants