Skip to content

Sql 0.9.1 #2621

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.

Sign up for GitHub

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

Merged
lmazuel merged 2 commits into from
May 24, 2018
Merged

Sql 0.9.1 #2621

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
32700b8
Generated from 3ea886e5b032ce36874bc94f08cd4ca294a666cd
lmazuel May 24, 2018
1a2cbff
SQL packaging
lmazuel May 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 19 additions & 9 deletions azure-mgmt-sql/HISTORY.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,16 @@
Release History
===============

0.9.1 (2018-05-24)
++++++++++++++++++

**Features**

- Managed instances, databases, and failover groups
- Vulnerability assessments
- Backup short term retention policies
- Elastic Jobs

0.9.0 (2018-04-25)
++++++++++++++++++

Expand All @@ -24,7 +34,7 @@ This version uses a next-generation code generator that *might* introduce breaki

- Return type changes from `msrestazure.azure_operation.AzureOperationPoller` to `msrest.polling.LROPoller`. External API is the same.
- Return type is now **always** a `msrest.polling.LROPoller`, regardless of the optional parameters used.
- The behavior has changed when using `raw=True`. Instead of returning the initial call result as `ClientRawResponse`,
- The behavior has changed when using `raw=True`. Instead of returning the initial call result as `ClientRawResponse`,
without polling, now this returns an LROPoller. After polling, the final resource will be returned as a `ClientRawResponse`.
- New `polling` parameter. The default behavior is `Polling=True` which will poll using ARM algorithm. When `Polling=False`,
the response of the initial call will be returned without polling.
Expand All @@ -40,7 +50,7 @@ This version uses a next-generation code generator that *might* introduce breaki
* ElasticPool.sku has replaced ElasticPool.dtu. Elastic pool scale can be set by setting Sku.name to the requested sku name (e.g. StandardPool, PremiumPool, or GP_Gen4) and setting Sku.capacity to the scale measured in DTU or vCores.
* ElasticPool.per_database_settings has replaced ElasticPool.database_dtu_min and ElasticPool.database_dtu_max.
- Database.max_size_bytes is now an integer instead of string.
- LocationCapabilities tree has been changed in order to support capabilities of new vCore-based database and elastic pool editions.
- LocationCapabilities tree has been changed in order to support capabilities of new vCore-based database and elastic pool editions.

**Features**

Expand All @@ -49,7 +59,7 @@ This version uses a next-generation code generator that *might* introduce breaki

* Removed support for managing Vaults used for Long Term Retention V1
* Changed BackupLongTermRetentionPolicy class, removing the Long Term Retention V1 properties and adding the Long Term Retention V2 properties
* Removed BackupLongTermRetentionPolicyState
* Removed BackupLongTermRetentionPolicyState

0.8.6 (2018-03-22)
++++++++++++++++++
Expand Down Expand Up @@ -103,16 +113,16 @@ This version uses a next-generation code generator that *might* introduce breaki

**Disclaimer**

We were using a slightly unorthodox convention for some operation ids.
Some resource operations were "nested" inside others, e.g. blob auditing policies was nested inside databases as in client.databases.get_blob_auditing_policies(..)
We were using a slightly unorthodox convention for some operation ids.
Some resource operations were "nested" inside others, e.g. blob auditing policies was nested inside databases as in client.databases.get_blob_auditing_policies(..)
instead of the flattened ARM standard client.database_blob_auditing_policies.get(...).

This convention has lead to some inconsistencies, makes some APIs difficult to find, and is at odds with future APIs.
For example if we wanted to implement listing db audit policies by server, continuing the current convention would be
This convention has lead to some inconsistencies, makes some APIs difficult to find, and is at odds with future APIs.
For example if we wanted to implement listing db audit policies by server, continuing the current convention would be
client.databases.list_blob_auditing_policies_by_server(..) which makes much less sense than the ARM standard which would beclient.database_blob_auditing_policies.list_by_server(...)`.

In order to resolve this and provide a good path moving forward,
we have renamed the inconsistent operations to follow the ARM standard.
In order to resolve this and provide a good path moving forward,
we have renamed the inconsistent operations to follow the ARM standard.
This is an unfortunate breaking change, but it's best to do now while the SDK is still in preview and since most of these operations were only recently added.

**Breaking changes**
Expand Down
Loading