Package: azure-mgmt-datalake-store
Microsoft Azure SDK for PythonThis is the Microsoft Azure Data Lake Store Management Client Library.Azure Resource Manager (ARM) is the next generation of management APIs that
replace the old Azure Service Management (ASM).This package has been tested with Python 2.7, 3.4, 3.5 and 3.6.For the older Azure Service Management (ASM) libraries, seeazure-servicemanagement-legacylibrary.For a more complete set of Azure libraries, see theazurebundle package.CompatibilityIMPORTANT: If you have an earlier version of the azure package
(version < 1.0), you should uninstall it before installing this package.You can check the version using pip:pipfreezeIf you see azure==0.11.0 (or any version below 1.0), uninstall it first:pipuninstallazureUsageFor code examples, seeData Lake Store Managementon docs.microsoft.com.Provide FeedbackIf you encounter any bugs or have suggestions, please file an issue in theIssuessection of the project.Release History0.5.0 (2018-06-14)FeaturesModel CreateDataLakeStoreAccountParameters has a new parameter virtual_network_rulesModel DataLakeStoreAccount has a new parameter virtual_network_rulesModel UpdateDataLakeStoreAccountParameters has a new parameter virtual_network_rulesAdded operation group VirtualNetworkRulesOperationsClient class can be used as a context manager to keep the underlying HTTP session open for performanceGeneral Breaking changesThis version uses a next-generation code generator thatmightintroduce breaking changes.Model signatures now use only keyword-argument syntax. All positional arguments must be re-written as keyword-arguments.
To keep auto-completion in most cases, models are now generated for Python 2 and Python 3. Python 3 uses the “*” syntax for keyword-only arguments.Enum types now use the “str” mixin (class AzureEnum(str, Enum)) to improve the behavior when unrecognized enum values are encountered.
While this is not a breaking change, the distinctions are important, and are documented here:https://docs.python.org/3/library/enum.html#othersAt a glance:“is” should not be used at all.“format” will return the string value, where “%s” string formatting will returnNameOfEnum.stringvalue. Format syntax should be prefered.New Long Running Operation:Return type changes frommsrestazure.azure_operation.AzureOperationPollertomsrest.polling.LROPoller. External API is the same.Return type is nowalwaysamsrest.polling.LROPoller, regardless of the optional parameters used.The behavior has changed when usingraw=True. Instead of returning the initial call result asClientRawResponse,
without polling, now this returns an LROPoller. After polling, the final resource will be returned as aClientRawResponse.Newpollingparameter. The default behavior isPolling=Truewhich will poll using ARM algorithm. WhenPolling=False,
the response of the initial call will be returned without polling.pollingparameter accepts instances of subclasses ofmsrest.polling.PollingMethod.add_done_callbackwill no longer raise if called after polling is finished, but will instead execute the callback right away.BugfixesCompatibility of the sdist with wheel 0.31.00.4.0 (2018-02-12)Breaking changesThe account operations object has been changed from “account” to “accounts”E.g., account.get(…) to accounts.get(…)When creating or updating resources (accounts, firewall rules, etc.), explicit parameter objects are now required:Account creation:“DataLakeStoreAccount” to “CreateDataLakeStoreAccountParameters”List of “FirewallRule” to “CreateFirewallRuleWithAccountParameters”List of “TrustedIdProvider” to “CreateTrustedIdProviderWithAccountParameters”Account update:“DataLakeStoreUpdateParameters” to “UpdateDataLakeStoreParameters”List of “FirewallRule” to “UpdateFirewallRuleWithAccountParameters”List of “TrustedIdProvider” to “UpdateTrustedIdProviderWithAccountParameters”Firewall rule creation and update:“FirewallRule” to “CreateOrUpdateFirewallRuleParameters”“FirewallRule” to “UpdateFirewallRuleParameters”Trusted identity provider creation and update:“TrustedIdProvider” to “CreateOrUpdateTrustedIdProviderParameters”“TrustedIdProvider” to “UpdateTrustedIdProviderParameters”0.3.0 (2018-01-09)Breaking changesChanged the ODataQuery parameter type from DataLakeStoreAccount to DataLakeStoreAccountBasic for these APIs:Account_ListAccount_ListByResourceGroupNotesAdded two more states to DataLakeStoreAccountStatus enum: Undeleting and CanceledAdded new Account APIs:Account_CheckNameAvailabilityLocation_GetCapabilityOperation_List0.2.0 (2017-08-17)Breaking changeWhen getting a list of accounts, the object type that is returned is DataLakeAnalyticsAccountBasic and not DataLakeAnalyticsAccount (more information on the difference is below in the Notes section)Standardized the parameter name for file paths in the url (e.g. fileDestination to path)NotesWhen getting a list of accounts, the account information for each account now includes a strict subset of the account information that is returned when getting a single accountThere are two ways to get a list of accounts: List and ListByResource methodsThe following fields are included in the account information when getting a list of accounts, which is less than the account information retrieved for a single account:provisioningStatestatecreationTimelastModifiedTimeendpointWhen retrieving account information, an account id field called “accountId” is now included.accountId’s description: The unique identifier associated with this Data Lake Analytics account.0.1.6 (2017-06-19)Fixing a regression discovered in 0.1.5. Please update to 0.1.6 to avoid any issues caused by that regression.0.1.5 (2017-06-07)New featuresAdd support for updating a User Managed KeyVault key.0.1.4 (2017-04-20)This wheel package is now built with the azure wheel extension0.1.3 (2017-02-13)New featuresAdded extended firewall rule support, enabling allowing/blocking all azure IP trafficAdd Update support for existing firewall rules (instead of replace)Added support for updating existing trusted identity providers (instead of replace)Fix various documentation bugs to reflect accurate information.0.1.2 (2017-01-09)New featuresAdded the ability to create and update accounts with usage commitment levels for Data Lake Store and Data Lake Analytics0.1.1 (2016-12-12)Breaking change“account_name” parameter is now “name” in account operation0.1.0 (2016-11-14)Initial Release