Skip to content

Adding Online Experimentation data plane API.#33135

Merged
smichtch merged 41 commits intomainfrom
feature/online-experimentation
Apr 21, 2025
Merged

Adding Online Experimentation data plane API.#33135
smichtch merged 41 commits intomainfrom
feature/online-experimentation

Conversation

@smichtch
Copy link
Copy Markdown
Member

@smichtch smichtch commented Mar 11, 2025

Data 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.

spec_pr_review_workflow_diagram

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.

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.

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.

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

Tooling

Guidelines & Specifications

Helpful Links

Getting help

  • First, please carefully read through this PR description, from top to bottom.
  • 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.
  • 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.

fix #33168

@smichtch smichtch requested a review from a team as a code owner March 11, 2025 20:31
@smichtch smichtch requested review from JeffreyRichter and mikekistler and removed request for a team March 11, 2025 20:31
@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app Bot commented Mar 11, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app Bot commented Mar 11, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@azure-sdk
Copy link
Copy Markdown
Collaborator

azure-sdk commented Mar 11, 2025

API Change Check

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

Language API Review for Package
TypeSpec Azure.Analytics.OnlineExperimentation
Go sdk/analytics/azonlineexperimentation
Swagger Microsoft.OnlineExperimentation
Java com.azure:azure-analytics-onlineexperimentation
JavaScript @azure-rest/analytics-onlineexperimentation
Python azure-onlineexperimentation

@smichtch smichtch force-pushed the feature/online-experimentation branch 2 times, most recently from 3313ce6 to 1f6fc42 Compare March 11, 2025 21:36
@smichtch smichtch force-pushed the feature/online-experimentation branch from 1f6fc42 to 8e94f14 Compare March 11, 2025 21:38
@smichtch smichtch force-pushed the feature/online-experimentation branch 5 times, most recently from 9939bf1 to 297e162 Compare March 12, 2025 15:44
@smichtch smichtch added the offline-review-requested Service team has requested PR review be conducted offline. label Mar 12, 2025
Comment on lines +49 to +54
- code: AvoidAnonymousTypes
- code: PatchInOperationName
- code: OperationIdNounVerb
- code: RequiredReadOnlyProperties
- code: SchemaNamesConvention
- code: SchemaDescriptionOrTitle
Copy link
Copy Markdown
Member

@weidongxu-microsoft weidongxu-microsoft Apr 17, 2025

Choose a reason for hiding this comment

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

Is this suppression from some template in specs (andthere seems no PatchInOperationName in this PR)?

Copy link
Copy Markdown
Member

@weidongxu-microsoft weidongxu-microsoft Apr 17, 2025

Choose a reason for hiding this comment

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

Thanks. Added Approved-Suppression label, as all these suppressions are from template readme

### Suppress non-TypeSpec SDK related linting rules
These set of linting rules aren't applicable to the new TypeSpec SDK code generators so suppressing them here. Eventually we will
opt-out these rules from running in the linting tools for TypeSpec generated swagger files.
```yaml
suppressions:
- code: AvoidAnonymousTypes
- code: PatchInOperationName
- code: OperationIdNounVerb
- code: RequiredReadOnlyProperties
- code: SchemaNamesConvention
- code: SchemaDescriptionOrTitle
```
### Suppress rules that might be fixed
These set of linting rules we expect to fixed in typespec-autorest emitter but for now suppressing.
Github issue filed at https://github.com/Azure/typespec-azure/issues/2762
```yaml
suppressions:
- code: LroExtension
- code: SchemaTypeAndFormat
- code: PathParameterSchema
```

Copy link
Copy Markdown
Member

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

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

Looks good! 👍

…rimentation/tspconfig.yaml


Remove "analytics" segment from python SDK package name.

Co-authored-by: catalinaperalta <9859037+catalinaperalta@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. Approved-Suppression data-plane new-api-version offline-review-requested Service team has requested PR review be conducted offline. PipelineBotTrigger PublishToCustomers Acknowledgement the changes will be published to Azure customers. SuppressionReviewRequired TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ExP - Managed - Online Experimentation] API Review

9 participants