Skip to content

Latest commit

 

History

History
113 lines (93 loc) · 7.61 KB

ChangeLog.md

File metadata and controls

113 lines (93 loc) · 7.61 KB
Raw

Current Release

Version 5.0.0

  • NOTE: This is a breaking change release. Please see the migration guide (https://aka.ms/azps-migration-guide) for a full list of breaking changes introduced.
  • Removed the Obsolete Properties fields in PSDataLakeStoreAccount.cs and its assoicated files
  • Changed one of the two OutputTypes of Get-AzureRmDataLakeStoreAccount
    • List<PSDataLakeStoreAccount> to List<PSDataLakeStoreAccountBasic>
    • The properties of PSDataLakeStoreAccountBasic is a strict subset of the properties of PSDataLakeStoreAccount
    • The additional properties that are in PSDataLakeStoreAccount are not returned by the service. Therefore, this change is to reflect this accurately. These additional properties are still in PSDataLakeStoreAccountBasic, but they are tagged as Obsolete.
  • Add support for online help
    • Run Get-Help with the -Online parameter to open the online help in your default Internet browser

Version 4.4.1

Version 4.4.0

Version 4.3.1

Version 4.3.0

Version 4.2.1

Version 4.2.0

  • Added support for user managed KeyVault key rotations in the Set-AzureRMDataLakeStoreAccount cmdlet
  • Added a quality of life update to automatically trigger an enableKeyVault call when a user managed KeyVault is added or a key is rotated.
  • Updated the token audience for job and catalog APIs to use the correct Data Lake specific audience instead of the Azure Resource audience.
  • Fixed a bug limiting the size of files created/appended using the following cmdlets:
    • New-AzureRmDataLakeStoreItem
    • Add-AzureRmDataLakeStoreItemContent

Version 4.1.0

  • Enable-AzureRmDataLakeStoreKeyVault (Enable-AdlStoreKeyVault)
    • Enable KeyVault managed encryption for a DataLake Store

Version 4.0.1

Version 4.0.0

  • For Import-AzureRMDataLakeStoreItem and Export-AzureRMDataLakeStoreItem trace logging has been disabled by default to improve performance. If trace logging is desired please use the -DiagnosticLogLevel and -DiagnosticLogPath parameters
  • Fixed a bug that would sometimes cause PowerShell to crash when uploading lots of small file to ADLS.

Version 3.6.0

  • Add support for head and tail to the Get-AzureRMDataLakeStoreItemContent cmdlet. This enables returning the top N or last N new line delimited rows to be displayed.

Version 3.5.0

Version 3.4.0

  • Update Upload and Download commands to use the new and improved Upload/Download helpers in the new DataLake.Store clients. This also gives better diagnostic logging, if enabled.
  • Default thread counts for Upload and download are now computed on a best effort basis based on the data being uploaded or downloaded. This should allow for good performance without specifying a thread count.
  • Update to Set-AzureRMDataLakeStoreAccount to allow for enabling and disabling Azure originating IPs through the firewall
  • Add warnings to Add and Set-AzureRMDataLakeStoreFirewallRule and AzureRMDataLakeStoreTrustedIdProvider if they are disabled
  • Remove explicit restrictions on resource locations. If Data Lake Store is not supported in a region, we will surface an error from the service.

Version 3.3.0

  • Updated help for all cmdlets to include output as well as more descriptions of parameters and the inclusion of aliases.
  • Update New-AdlStore and Set-AdlStore to support commitment tier options for the service.
  • Added OutputType mismatch warnings to all cmdlets with incorrect OutputType attributes. These will be fixed in a future breaking change release.
  • Add Diagnostic logging support to Import-AdlStoreItem and Export-AdlStoreItem. This can be enabled through the following parameters:
    • -Debug, enables full diagnostic logging as well as debug logging to the PowerShell console. Most verbose options
    • -DiagnosticLogLevel, allows finer control of the output than debug. If used with debug, this is ignored and debug logging is used.
    • -DiagnosticLogPath, optionally specify the file to write diagnostic logs to. By default it is written to a file under %LOCALAPPDATA%\AdlDataTransfer
  • Added support to New-AdlStore to explicitly opt-out of account encryption. To do so, create the account with the -DisableEncryption flag.

Version 3.2.0

  • Introduction of deprecation warning for nested properties for all ARM resources. Nested properties will be removed in a future release and all properties will be moved one level up.
  • Removed the ability to set encryption in Set-AzureRMDataLakeStoreAccount (never was supported)
  • Added ability to enable/disable firewall rules and the trusted id providers during Set-AzureRMDataLakeStoreAccount
  • Added a new cmdlet: Set-AzureRMDataLakeStoreItemExpiry, which allows the user to set or remove the expiration for files (not folders) in their ADLS account.
  • Small fix for friendly date properties to pivot off UTC time instead of local time, ensuring standard time reporting.

Version 3.1.0

  • Improvements to import and export data cmdlets
    • Drastically increased performance for distributed download scenarios, where multiple sessions are running across many clients targeting the same ADLS account.
    • Better error handling and messaging for both upload and download scenarios.
  • Full Firewall rules management CRUD
    • The below cmdlets can be used to manage firewall rules for an ADLS account:
    • Add-AzureRMDataLakeStoreFirewallRule
    • Set-AzureRMDataLakeStoreFirewallRule
    • Get-AzureRMDataLakeStoreFirewallRule
    • Remove-AzureRMDataLakeStoreFirewallRule
  • Full Trusted ID provider management CRUD
    • The below cmdlets can be used to manage trusted identity providers for an ADLS account:
    • Add-AzureRMDataLakeStoreTrustedIdProvider
    • Set-AzureRMDataLakeStoreTrustedIdProvider
    • Get-AzureRMDataLakeStoreTrustedIdProvider
    • Remove-AzureRMDataLakeStoreTrustedIdProvider
  • Account Encryption Support
    • You can now encrypt newly created ADLS accounts as well as enable encryption on existing ADLS accounts using the New-AzureRMDataLakeStoreAccount and Set-AzureRMDataLakeStoreAccount cmdlets, respectively.