Skip to content

Relay: RP version 2017-04-01 #4380

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 12 commits into from
Aug 4, 2017
Merged

Conversation

v-Ajnava
Copy link

@v-Ajnava v-Ajnava commented Jul 28, 2017

Description

PR consist the changes related RP version 2017-04-01


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.

{
Rights.Add(teset.ToString());
}
//Rights = authorizationrule.Rights.Select(x => Enum.Parse(typeof(AccessRights?), x))
Copy link
Member

Choose a reason for hiding this comment

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

remove commented code

Copy link
Author

Choose a reason for hiding this comment

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

Removed.


Rights = new List<string>();

foreach (AccessRights teset in authorizationrule.Rights)
Copy link
Member

Choose a reason for hiding this comment

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

teset == typo?

Copy link
Author

Choose a reason for hiding this comment

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

corrected to a meaningful name

@@ -46,7 +46,7 @@ public AuthorizationRuleKeysAttributes(string primaryConnectionString = default(
/// Initializes a new instance of the AuthorizationRuleKeysAttributes class with a Azure.Management.Relay.Models.AuthorizationRuleKeys
/// </summary>
/// <param name="authorizationruleskeys"></param>
public AuthorizationRuleKeysAttributes(AuthorizationRuleKeys authorizationruleskeys)
public AuthorizationRuleKeysAttributes(AccessKeys authorizationruleskeys)
Copy link
Member

Choose a reason for hiding this comment

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

Did the type of an output type or parameter type change? Were there any properties removed?

Copy link
Author

Choose a reason for hiding this comment

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

just the name has been changed in the SDK, properties are same and cmdlet dosent expose it.

@@ -40,7 +40,7 @@ public RelayNamespaceAttirbutesUpdateParameter(IDictionary<string, string> tags
Tags = tags;
}

public RelayNamespaceAttirbutesUpdateParameter(RelayNamespaceUpdateParameter relaynamespaceupdateparameter)
public RelayNamespaceAttirbutesUpdateParameter(RelayUpdateParameters relaynamespaceupdateparameter)
Copy link
Member

Choose a reason for hiding this comment

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

does this new type have all the properties of the old type? If not, is this exposed via cmdlet output or parameters?

Copy link
Author

Choose a reason for hiding this comment

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

the new type has all the same properties just the name has been changed and its not exposed via cmdlet output or parameters.

REDMOND\v-ajnava added 2 commits July 31, 2017 12:38
…nto Relaypwr2017

# Conflicts:
#	src/ResourceManager/Relay/Commands.Relay/Commands.Relay.csproj
#	src/ResourceManager/Relay/Commands.Relay/packages.config
markcowl
markcowl previously approved these changes Aug 1, 2017
@markcowl
Copy link
Member

markcowl commented Aug 1, 2017

@markcowl
Copy link
Member

markcowl commented Aug 1, 2017

@azuresdkci retest this please

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

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

@v-Ajnava @markcowl waiting for Ajit to make one last change mentioned offline

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

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

@v-Ajnava a couple comments as a result of the merge after the Common.Dependencies project went through

@@ -41,10 +41,71 @@
<Prefer32Bit>false</Prefer32Bit>
</PropertyGroup>
<ItemGroup>
<Reference Include="Microsoft.Azure.Management.Relay, Version=0.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
Copy link
Member

Choose a reason for hiding this comment

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

@v-Ajnava please revert the changes made in this file. I assume they are a result of a merge conflict after our Common.Dependencies PR went through. The only thing that should be in csproj files should be the management libraries that the project depends on. In this case, it should just be the Relay management library. Everything else is defined in Common.Dependencies.targets

Copy link
Author

Choose a reason for hiding this comment

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

Removed the other than required dependencies

<package id="Microsoft.Azure.Management.Resources" version="2.20.0-preview" targetFramework="net45" />
<package id="Microsoft.Azure.Management.Storage" version="3.0.0" targetFramework="net45" />
<package id="Microsoft.Azure.Management.Websites" version="1.2.0-preview" targetFramework="net45" />
<package id="Microsoft.Bcl" version="1.1.9" targetFramework="net45" />
Copy link
Member

Choose a reason for hiding this comment

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

@v-Ajnava similar comment to the one made in the csproj file. The packages.config file should only have a reference on the management packages you need.

Copy link
Author

Choose a reason for hiding this comment

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

Removed the other than required dependencies

<Reference Include="Microsoft.Azure.Common.NetFramework">
<HintPath>..\..\..\packages\Microsoft.Azure.Common.2.1.0\lib\net45\Microsoft.Azure.Common.NetFramework.dll</HintPath>
</Reference>
<Reference Include="Microsoft.Azure.Management.Relay, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
Copy link
Member

Choose a reason for hiding this comment

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

You only need the relay reference in this file. The rest come from the comnmon dependences target

Copy link
Author

Choose a reason for hiding this comment

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

Removed other dependencies

Copy link
Member

Choose a reason for hiding this comment

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

@v-Ajnava extra dependencies are still showing up in this file

Copy link
Author

Choose a reason for hiding this comment

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

Removed the Extra dependencies

@cormacpayne cormacpayne changed the base branch from preview to release-4.3.0 August 4, 2017 16:03
@cormacpayne
Copy link
Member

@cormacpayne cormacpayne merged commit f9acea2 into Azure:release-4.3.0 Aug 4, 2017
@v-Ajnava v-Ajnava deleted the Relaypwr2017 branch April 12, 2018 01:17
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