Skip to content

Merge from Azure/azure-powershell/master #21

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 10,000 commits into from
Nov 17, 2016
Merged

Merge from Azure/azure-powershell/master #21

merged 10,000 commits into from
Nov 17, 2016

Conversation

jtlibing
Copy link
Owner

Description


This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

General Guidelines

  • 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.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • Pull request includes test coverage for the included changes.
  • PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThrough parameter.

Cmdlet Parameter Guidelines

  • Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

smithaborkar and others added 30 commits October 4, 2016 10:38
Adding AuthenticodeSign verification task. Adding test for the task
…ding module manifest, adding VS Dev command prompt with powershell, moving existing scripts that have been consolidated into module to a legacyscript directory
NH change in sas Rules and Regenerate Key api : net sdk 2.0.0
Adding test framework documentation
platyPS documentation and Profile conversion
Add additional check to prevent null-reference exception
Fix storage account name hardcoded in diagnostics test files
athipp and others added 29 commits October 28, 2016 10:43
…or to cmdlet processing and then asserting on the actual count. On CI the initial count was more than zero, but locally it is alwasy zero
ADL Updates to latest SDK in preparation for GA
Adding PsVersion to userAgent
- Administrators to Administrator
- Included AnalysisServices module in AzureRM
powershel modules for AnalysisServices
[Release 3.1.0] Update change log and module manifest files
[Release 3.1.0] Merge release-3.1.0 -> master
* Need to check for null when creating Tags.

* 1. Added new new param:TunnelConnectionStatus in output object:VirtualNetworkGatewayConnection and 2. Added new optional input param:gatewayVip in ResetGateway API.

* Fix build error due to error in help file

* Fixing bugs and modifying tests for analysis services commands

- Added ServerFullName property to powershell  type.
- Modified tests to validate.

* Incorporate review comments

* revert back common.ps1

* Updated changeLog as per comments

* Fix changeLog file

* Bumping module version to 3.2.0 for AzureRm and AzureRm.Network
@jtlibing jtlibing merged commit a9cef22 into jtlibing:dev2 Nov 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.