Skip to content
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

Upgrading from rest client v2022_05_01 to v2022_10_01version for datastore type #28293

Merged

Conversation

maykumar-msft
Copy link
Contributor

Description

Upgrading 'DatastoreType' from v2022_05_01 to v2022_10_01

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

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.

@ghost ghost added the Machine Learning label Jan 11, 2023
@maykumar-msft maykumar-msft changed the title upgrading model version for datastore type Upgrading from rest client v2022_05_01 to v2022_10_01version for datastore type Jan 11, 2023
@luigiw luigiw enabled auto-merge (squash) January 12, 2023 00:16
@luigiw luigiw disabled auto-merge January 12, 2023 22:09
@luigiw
Copy link
Contributor

luigiw commented Jan 12, 2023

/check-enforcer override

@luigiw luigiw merged commit 3b9a93c into Azure:main Jan 13, 2023
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants