You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Pipelines:
Successfully started running 2 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The package metadata contains incorrect repository and homepage paths, and the README misidentifies the provisioned service as Azure SignalR Service instead of Azure Web PubSub.
Adds the first preview of @azure/provisioning-webpubsub to the Azure SDK monorepo. The package provides typed Web PubSub resources for authoring infrastructure definitions using @azure/provisioning-core, without modifying live Azure resources.
Changes:
Adds nine resource classes covering Web PubSub services and child resources.
Adds schema probes, documentation snippets, and Bicep/JSON rendering baselines.
Integrates package builds, API reports, dependencies, and management CI.
Package-relative paths below are under sdk/web-pubsub/provisioning-webpubsub/; repository-level paths are shown in full.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The shared-private-link scenarios construct incorrect resource types or use an empty request fixture, leaving the intended resource scopes and link properties unvalidated.
This shared-private-link scenario constructs only a replica, and its {} request fixture makes the Swagger assertion pass without checking any link properties. Reference the replica as existing, create a WebPubSubReplicaSharedPrivateLink child from the source request, and update the asserted resource type, request fixture, and Bicep/JSON baselines together.
This service-scoped shared-private-link example constructs a replica-scoped link, so its baseline validates /webPubSub/replicas/sharedPrivateLinkResources instead of /webPubSub/sharedPrivateLinkResources. Sharing the request-body shape does not check the source operation's resource scope. Use WebPubSubSharedPrivateLink with service as its parent, remove the unused replica, and update the asserted resource type and both baselines.
This shared-private-link scenario constructs and selects only the parent Replica. With {} as the Swagger fixture, the request comparison passes for any rendered object without validating a shared private link or its properties. Reference an existing replica, construct WebPubSubReplicaSharedPrivateLink with the source request payload, and update the selected resource type, request fixture, and output baselines.
Updated README to reflect the new library name and its purpose.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The Swagger example’s empty expected object validates no request properties, and its scenario constructs only the parent Replica instead of the shared-private-link resource.
✅ All CI checks have passed. The PR is only marked "blocked" because it is awaiting required review/approval, so it is ready for review.
The SDK engineer will review this PR shortly. Once it's approved, you can go ahead and merge it. To make things easier, feel free to enable auto-merge so it gets auto merged right after approval.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MgmtThis issue is related to a management-plane library.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SDK generation details
Note
This pull request was generated automatically.
specification/webpubsub/resource-manager/Microsoft.SignalRService/SignalRService/tspconfig.yamlata75e2ceImportant
Complete the SDK release prerequisites before release.
fixes https://github.com/Azure/js-provisioning-lib/issues/514