Skip to content
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

update ps with network SDK with Network 11.1.0 #4265

Merged
merged 14 commits into from
Jul 8, 2017

Conversation

DeepakRajendranMsft
Copy link
Contributor

@DeepakRajendranMsft DeepakRajendranMsft commented Jul 6, 2017

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 PassThru 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.

@DeepakRajendranMsft
Copy link
Contributor Author

@markcowl @shahabhijeet @cormacpayne this is the PR to increase the network sdk

@DeepakRajendranMsft
Copy link
Contributor Author

@DeepakRajendranMsft
Copy link
Contributor Author

@DeepakRajendranMsft
Copy link
Contributor Author

@DeepakRajendranMsft
Copy link
Contributor Author

@@ -600,10 +600,18 @@
<Project>{70527617-7598-4aef-b5bd-db9186b8184b}</Project>
<Name>Commands.Common.Authentication.Abstractions</Name>
</ProjectReference>
<ProjectReference Include="..\..\..\Common\Commands.Common.Authentication\Commands.Common.Authentication.csproj">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not add this reference. You should only have a reference to the abstractions class.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

<ProjectReference Include="..\..\..\Common\Commands.Common\Commands.Common.csproj">
<Project>{5ee72c53-1720-4309-b54b-5fb79703195f}</Project>
<Name>Commands.Common</Name>
</ProjectReference>
<ProjectReference Include="..\..\Common\Commands.Common.Authentication.ResourceManager\Commands.Common.Authentication.ResourceManager.csproj">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not add this reference. You may need to build this as part of your solution, but it cannot be a dependency of your management cmdlets

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

"D:\workspace\powershell-demand\src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Compute\Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.Automation.ConvertToAzureRmVMManagedDisk","ConvertTo-AzureRmVMManagedDisk","0","1050","The parameter set 'InvokeByDynamicParameters' for cmdlet 'ConvertTo-AzureRmVMManagedDisk' has been removed.","Add parameter set 'InvokeByDynamicParameters' back to cmdlet 'ConvertTo-AzureRmVMManagedDisk'."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like none of these changes should be necessary

public uint Protocol { get; set; }
public uint RemoteIPAddress { get; set; }
public uint RemotePort { get; set; }
public int Protocol { get; set; }
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file is not even being used... should be removed. will check with Irina and follow up

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the file can be removed

markcowl
markcowl previously approved these changes Jul 7, 2017
@markcowl
Copy link
Member

markcowl commented Jul 7, 2017

@akshaysngupta
Copy link
Member

LGTM

@DeepakRajendranMsft
Copy link
Contributor Author

@markcowl markcowl merged commit 42b838b into Azure:release-4.2.0 Jul 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants