forked from Azure/azure-powershell
-
Notifications
You must be signed in to change notification settings - Fork 0
huangpf PR: dev <- Azure:dev #571
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Details: Start-AzureRmSiteRecoveryPlannedFailoverJob -Direction RecoverytoPrimary -RecoveryPlan/-ProtectedEntity [-Optimize ForDownTime/ForSynchronization] [-CreateVmIfNotFound Yes/No [-Server <ASRServerObject>]] -CreateVmIfNotFound : Accepts one of two options. Yes|No. Default is No, so if not specified assume no -Server: Specify an ASR server (Hyper-V host on which to create the VM if it doesn’t exist).
…ultSettings - parameter naming and help text issues
…h a Force parameter
…with a Force parameter
…KeyVaultServiceEndpointResourceId of Get-AzureRmEnvironment. The keyvault resource Id is now obtained from server using 401 challenge. The Azure PowerShell common infrastructure currently do not support this in an intuitive fashion, so tweaking its usage by overriding the environment endpoint value before acquiring the token.
…essPolicy to support CSP
…VaultAccessPolicy to support CSP" This reverts commit 6cf10fa.
* Update PowerShell to use the latest SDK * Missed DataLakeStore upgrade. * Updates for file and folder download. Tests will be in the next iteration. * Fixing the connection manager overwriting. This is important to ensure that we have enough connections available for ingress/egress scenarios, and it must be set before the client is first used. * Updating the help for ADLS to include new download. * Signed local package for testing. * Add full path property to ADLS Items * Remove private package. Official is published * Adding official package from nuget. * Missed one disable of tracing. * Fixing ADL tests and re-running them This enables ADL tests to run during CI and gets them totally updated. * fix to always copy ADL session records. * Add links to AzureRM.Resources.ps1 Following the pattern from compute tests. * Adding records directory info for mock server This is a requirement for the tests to be discovered when run in playback mode. * Fix ADL tests and update changelog This updates the change log to reflect the changes made Fixes to datetime offset for listing jobs fix to import/export logic due to inverted parameters. * Missed one of the test updates * test fixes for ADLA and ADLS * Add specific exclusion for ADL acls Inside of ACLs we allow ":", which breaks the playback of tests, since it encodes ":", which results in a missed match in the recorded json (which contains the colon). This fixes that so playback does not encode colons for paths that start with: /webhdfs/v1/?aclspec
…lags Removing flags which are not supported by azure-chef-extension now
…eyVaultAccessPolicy
* Aligned versions of references to: * Microsoft.Rest.ClientRuntime to 2.1.0 * Microsoft.Rest.ClientRuntime.Azure to 3.1.0 * Microsoft.Rest.ClientRuntime.Azure.Authentication to 2.0.1 * Microsoft.IdentityModel.Clients.ActiveDirectory to 2.18 * Newtonsoft.Json to 6.0.8 (cherry picked from commit 98a2387) (cherry picked from commit 014e101) * Upgraded all solutions to Microsoft.IdentityModel.Clients.ActiveDirectory 2.26.305102204 (cherry picked from commit 1d38319) (cherry picked from commit fa3594c) * Removed nuget sources from Cdn/NuGet.Config * Fixed StaticAnalysis project build break (cherry picked from commit 6d66344) (cherry picked from commit b4bb218) * Upgraded reference to ClientRuntime.Authentication 2.2.3-preview for ADAL 2.26 reference * Upgraded reference to ClientRuntime.TestFramework 1.2.5 * Upgraded to ADAL 2.27.
…orkload (#2519) * 1.Added backup support for Azure SQL workload 2.Added capability to specify retention of recovery point during backup 3.Added backup support for Encrypted VMs in the Azure VM workload * Removing SubType in csproj, format ps1 xml indent Correction and adding storage package in package.config * Adding summary to public functions for Azure sql * Indentation in RecoveryPointConversion.cs and summary fix in AzureSqlRecoveryPoint.cs * Uncommenting RecoveryServices.Backup test assembly, update error message for blob storage account, making resource id parsing generic * [RS Backup] Addressed review comments, fixed a few minor bugs 1. Long line breaks. Set 100 as the line length limit 2. Fixed bug: Get-AzureRmRecoveryServicesBackupContainer printing internal Vm Unique Id as Name 3. Added Deprecation message for Name filter in Get-AzureRmRecoveryServicesBackupContainer and introduced FriendlyName filter 4. Fixed resource group filter case-sensitive issue in Get-Item cmdlet * [RS Backup] Adding csproj reference to Commands.RecoveryServices in Tests project * [RS Backup] Onboarding RS Backup Tests project onto test targets * [RS Backup] Added RecoveryServices module to test setup * [RS Backup] Universal time fix in test * [RS Backup] Universal time fix in job tests * Excluding change for blocking blob storage account for restore * [RS Backup] Removed hardcoded location in vault tests * [RS Backup] Returning single location instead of array of locations in get_available_location function * [RS Backup] Making the vault location parameter local to test functions * [RS Backup] Fixing a test issue - using absolute path when doing path check * [RS Backup] bug fix - Get Recovery Point Id is returning incorrect ContainerName and ItemName in Powershell
Adding code to remove dependency with AzureKeyVaultServiceEndpointResourceId
Azure Site Recovery Bug Fixes and adding deprecation warning for RDFE cmdlets.
Add new parameter to command Set-AzureRmKeyVaultAccessPolicy
Normalize confirmation for all cmdlets that have a Force parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.