Skip to content

dpg, upgrade webpubsub to 2022-11#32125

Merged
haolingdong-msft merged 36 commits intoAzure:mainfrom
haolingdong-msft:webpubsub-upgrade-2022-11
Jan 6, 2023
Merged

dpg, upgrade webpubsub to 2022-11#32125
haolingdong-msft merged 36 commits intoAzure:mainfrom
haolingdong-msft:webpubsub-upgrade-2022-11

Conversation

@haolingdong-msft
Copy link
Member

@haolingdong-msft haolingdong-msft commented Nov 14, 2022

Description

Fix #31975.
azure-rest-api-spec: Azure/azure-rest-api-specs#20762

  1. Regen and update source code. Highlights:
    • Regen based on new API version.
    • The Impl classes under 'impl' folder are all generated.
    • Add removeConnectionFromAllGroupsWithResponse interface.
    • Support query group for /api/hubs/{hub}/:generateToken.
    • use empty string "" as content type to pass non-null check in impl classes, I have checked in LIVE test that the content-type passed in through RequestOptions appears in the real HTTP request.
  2. Add related tests.
  3. Add samples on filters.
  4. Update CHANGELOG, readme.md and pom.xml.
  5. Existing bug fix on WebPubSubServiceClient.getClientAccessToken()

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.

@azure-sdk
Copy link
Collaborator

API change check

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

azure-messaging-webpubsub

if (hub == null) {
return Mono.error(new IllegalArgumentException("Parameter hub is required and cannot be null."));
}
if (connectionId == null) {
return Mono.error(new IllegalArgumentException("Parameter connectionId is required and cannot be null."));
}
if (contentType == null) {
Copy link
Member Author

Choose a reason for hiding this comment

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

@srnagar Do we need this kind of validation on client side?

Copy link
Member

Choose a reason for hiding this comment

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

contentType is an explicit param in the method, so, checking for null is okay for explicit params.

Copy link
Member Author

Choose a reason for hiding this comment

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

ok, it's fine, the reason I ask this is that: I use empty string "" as content type to pass this non-null check (I have checked in LIVE test that the content-type passed in through RequestOptions appears in the real HTTP request). So would like to make sure if we really need this validation.

Copy link
Member

@vicancy vicancy left a comment

Choose a reason for hiding this comment

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

Thanks for your efforts! The PR looks great! Added some little comments.

assertResponse(client.sendToAllWithResponse(
BinaryData.fromString("Hello World - Broadcast test!"),
new RequestOptions().setHeader("Content-Type", "text/plain")
.addQueryParam("filter", "userId ne 'user1'")), 202);
Copy link
Member

Choose a reason for hiding this comment

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

How about adding a ClientConnectionFilter helper class, as similar to what azure search does with its SearchFilter

A similar approach in c# is here https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/webpubsub/Azure.Messaging.WebPubSub/src/ClientConnectionFilter.cs

@haolingdong-msft haolingdong-msft marked this pull request as ready for review December 20, 2022 07:13
### Features Added

### Breaking Changes
## 1.2.0 (Unreleased)
Copy link
Member

Choose a reason for hiding this comment

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

Please update the release date too.

Copy link
Member Author

Choose a reason for hiding this comment

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

sure, I will update before release. Plan to release next week (after core release finished)

requestOptions.addQueryParam("role", options.getRoles().stream().collect(Collectors.joining(",")));
}
if (CoreUtils.isNullOrEmpty(options.getGroups())) {
requestOptions.addQueryParam("group", options.getGroups().stream().collect(Collectors.joining(",")));
Copy link
Member

Choose a reason for hiding this comment

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

question: what if group name contains ,, will it be escaped?


List<String> expectedRoles = Arrays.asList("a", "b");
// test for special char case
List<String> expectedGroups = Arrays.asList("a&b", "c");
Copy link
Member Author

Choose a reason for hiding this comment

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

Also tested when name contains &

Copy link
Member Author

Choose a reason for hiding this comment

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

This test needs to use real webpubsub endpoint to generate client token in LIVE/RECORD mode and use recorded json in PLAYBACK mode. So I make TokenGenerationTest extends TestBase. But this will cause the existing parameterized tokenGeneration tests all needs playback file, otherwise it will have below error. Please let me know if you have any concern or suggestion.
java.lang.RuntimeException: Missing both new and old playback files

Copy link
Member

Choose a reason for hiding this comment

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

After the changes, does it test the key credential mode, or the AAD credential mode?

You can always skip PLAYBACK, if you only want to have LIVE tests.

Copy link
Member Author

@haolingdong-msft haolingdong-msft Jan 6, 2023

Choose a reason for hiding this comment

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

AAD credential mode. skipping PLAYBACK still needs to extends TestBase?

@haolingdong-msft haolingdong-msft force-pushed the webpubsub-upgrade-2022-11 branch from 9fd130c to 11d5d4e Compare January 5, 2023 09:51
requestOptions.addQueryParam("minutesToExpire", String.valueOf(options.getExpiresAfter().toMinutes()));
}
if (CoreUtils.isNullOrEmpty(options.getRoles())) {
if (!CoreUtils.isNullOrEmpty(options.getRoles())) {
Copy link
Member

Choose a reason for hiding this comment

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

Thanks for fixing this. Can you also add some tests to ensure these cases are covered?

Copy link
Member Author

@haolingdong-msft haolingdong-msft Jan 6, 2023

Choose a reason for hiding this comment

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

Tests are added. In the test, I tested generate token from Azure AD token credential, and use the existing test data which includes setting roles and groups, and I also add data on special characters like & and ,. /cc @vicancy

public void testTokenGenerationFromAadCredential(GetClientAccessTokenOptions tokenOptions, String connectionString,

public void testTokenGenerationFromAadCredential() throws ParseException {
@ParameterizedTest
@MethodSource("getTokenOptions")
@DoNotRecord(skipInPlayback = true)
Copy link
Member

Choose a reason for hiding this comment

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

remember to delete the json with token.

Copy link
Member

@weidongxu-microsoft weidongxu-microsoft left a comment

Choose a reason for hiding this comment

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

LGTM

good job on the fix.

Copy link
Member

@vicancy vicancy left a comment

Choose a reason for hiding this comment

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

Awesome work!

@haolingdong-msft haolingdong-msft merged commit 4876ed3 into Azure:main Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE REQ] update azure-messaging-webpubsub to 2022-11-01

5 participants