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

Password fields changes for November breaking change release #4664

Merged
merged 9 commits into from
Nov 1, 2017

Conversation

darshanhs90
Copy link
Contributor

@darshanhs90 darshanhs90 commented Sep 26, 2017

Related to #4359

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.

@markcowl
Copy link
Member

markcowl commented Sep 28, 2017

Do not merge until the branch is open for November breakign change release #Resolved

@markcowl
Copy link
Member

markcowl commented Oct 3, 2017

@darshanhs90 Please hold off on this PR until next week. Closing for now #Resolved

@markcowl markcowl closed this Oct 3, 2017
@darshanhs90 darshanhs90 reopened this Oct 26, 2017
@@ -72,8 +74,9 @@ public override void ExecuteCmdlet()
ObjectId = ActiveDirectoryClient.GetObjectIdFromApplicationId(ApplicationId);
}

string decodedPassword = Utilities.SecureStringToString(Password);
#pragma warning disable 0618
Copy link
Contributor

@maddieclayton maddieclayton Oct 26, 2017

Choose a reason for hiding this comment

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

You can remove the #pragma warnings because they were to suppress the obsolete warning. This also applies to all other files. #Resolved

@@ -12,10 +12,13 @@
// limitations under the License.
// ----------------------------------------------------------------------------------

using Microsoft.Azure.Commands.Resources;
Copy link
Contributor

@maddieclayton maddieclayton Oct 26, 2017

Choose a reason for hiding this comment

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

Are all three of these added dependencies being used? If not please delete all unnecessary usings from all files. #Resolved

@@ -72,8 +74,9 @@ public override void ExecuteCmdlet()
ObjectId = ActiveDirectoryClient.GetObjectIdFromApplicationId(ApplicationId);
}

string decodedPassword = Utilities.SecureStringToString(Password);
Copy link
Contributor

@maddieclayton maddieclayton Oct 26, 2017

Choose a reason for hiding this comment

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

Please use this conversion method instead (and change in other files). #Resolved

@@ -135,6 +135,7 @@
<Compile Include="Models.ResourceGroups\ResourceClient.ResourceManager.cs" />
<Compile Include="Properties\AssemblyInfo.cs" />
<Compile Include="Models.ResourceGroups\ResourceClient.cs" />
<Compile Include="Utilities\Utility.cs" />
Copy link
Contributor

@maddieclayton maddieclayton Oct 26, 2017

Choose a reason for hiding this comment

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

Remove this (don't need when you change to common conversion method). #Resolved

@@ -0,0 +1,34 @@
// ----------------------------------------------------------------------------------
Copy link
Contributor

@maddieclayton maddieclayton Oct 26, 2017

Choose a reason for hiding this comment

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

Remove this (don't need when you change to common conversion method). #Resolved

@maddieclayton
Copy link
Contributor

maddieclayton commented Oct 26, 2017

To fix your build issues, add your breaking changes errors here to the breaking changes file here. Let me know if this does not fix your build or if you have any questions. #Resolved

maddieclayton
maddieclayton previously approved these changes Oct 31, 2017
@maddieclayton
Copy link
Contributor

maddieclayton commented Oct 31, 2017

@darshanhs90 I think your recent changes broke these tests:
TestNewADServicePrincipal
TestNewADServicePrincipalWithoutApp
TestNewADApplication

Can you rerecord these tests? #Resolved

@maddieclayton maddieclayton dismissed their stale review October 31, 2017 19:34

Build failed

@darshanhs90
Copy link
Contributor Author

rerecorded and pushed the changes


In reply to: 340882176 [](ancestors = 340882176)

#pragma warning disable 0618
if (!string.IsNullOrEmpty(Password))
#pragma warning restore 0618
string decodedPassword = SecureStringExtensions.ConvertToString(Password);
Copy link
Contributor

@maddieclayton maddieclayton Oct 31, 2017

Choose a reason for hiding this comment

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

This will throw an error if Password is null, please decode once you've checked if Password is null or empty. #Resolved

#pragma warning disable 0618
if (!string.IsNullOrEmpty(Password))
#pragma warning restore 0618
string decodedPassword = SecureStringExtensions.ConvertToString(Password);
Copy link
Contributor

@maddieclayton maddieclayton Oct 31, 2017

Choose a reason for hiding this comment

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

Same #Resolved

#pragma warning disable 0618
if (!string.IsNullOrEmpty(Password))
#pragma warning restore 0618
string decodedPassword = SecureStringExtensions.ConvertToString(Password);
Copy link
Contributor

@maddieclayton maddieclayton Oct 31, 2017

Choose a reason for hiding this comment

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

Same #Resolved

@darshanhs90
Copy link
Contributor Author

darshanhs90 commented Oct 31, 2017

Made the changes as per the comments #Resolved

Copy link
Contributor

@maddieclayton maddieclayton left a comment

Choose a reason for hiding this comment

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

Two very small changes.

#pragma warning disable 0618
if (!string.IsNullOrEmpty(Password))
#pragma warning restore 0618
if (Password != null && Password.Length > 0)
Copy link
Contributor

@maddieclayton maddieclayton Oct 31, 2017

Choose a reason for hiding this comment

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

Nit: use if (!string.IsNullOrEmpty(Password)) as used previously

Apply to the other uses in this PR as well. #WontFix

Copy link
Contributor Author

Choose a reason for hiding this comment

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

since Password is a type of securestring,we cant use string.IsNullOrEmpty on that


In reply to: 148155448 [](ancestors = 148155448)

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah right, good catch.

if (!string.IsNullOrEmpty(Password))
#pragma warning restore 0618
{
if (Password != null && Password.Length > 0) {
Copy link
Contributor

@maddieclayton maddieclayton Oct 31, 2017

Choose a reason for hiding this comment

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

All beginning brackets should be on a new line. Please apply across this whole file. #Resolved

@cormacpayne
Copy link
Member

@maddieclayton
Copy link
Contributor

@azuresdkci test this please

@maddieclayton maddieclayton merged commit f2a2278 into Azure:preview Nov 1, 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.

5 participants