Skip to content

Adding ActivityLogAlerts and ActionGroups API calls, PATH operations, and the corresponding unit tests#3514

Closed
gucalder wants to merge 27 commits intoAzure:psSdkJson6from
AuxMon:activityAndAction
Closed

Adding ActivityLogAlerts and ActionGroups API calls, PATH operations, and the corresponding unit tests#3514
gucalder wants to merge 27 commits intoAzure:psSdkJson6from
AuxMon:activityAndAction

Conversation

@gucalder
Copy link
Copy Markdown
Contributor

Description


This checklist is used to make sure that common guidelines for a pull request are followed.

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.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
  • The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

gucalder and others added 25 commits April 17, 2017 16:45
…ure#3236)

* Renaming Management.Search to Microsoft.Azure.Management.Search

The package and assembly names were accidentally changed during the VS2017
migration. This fixes it.

* Search SDK: Updating Build-SearchPackages script
<PropertyGroup>
<Description>Microsoft Azure Monitor Library</Description>
<VersionPrefix>0.16.0-preview</VersionPrefix>
<VersionPrefix>0.16.1-preview</VersionPrefix>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@gucalder you have redundant tags, please remove versionPrefix and move the Version under the top PropertyGroup

<Description>Monitor.Tests Class library</Description>
<PackageId>Monitor.Tests</PackageId>
<VersionPrefix>1.0.0-preview</VersionPrefix>
<TargetFrameworks>net452</TargetFrameworks>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@gucalder any reason you want your tests to be targeting .NET 452?
If this was a mistake please remove

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is odd, as soon as I remove .Net 452 from this project file, VS builds, but it does not detect any unit test.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

BTW: I can only build from VS 2017, not from the command line, nor from the root of the repo.
Is that expected?
Do I need to use any special argument to build from the command line?

<ItemGroup>
<PackageReference Include="Microsoft.Azure.Management.ResourceManager" Version="1.5.0-preview" />
<ProjectReference Include="..\Management.Search\Management.Search.csproj" />
<ProjectReference Include="..\Management.Search\Microsoft.Azure.Management.Search.csproj" />
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@gucalder do you have any changes for the Search management SDK? Or was this is a mistake.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Definitely a mistake. I do not remember changing this file.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

In fact I do not know how or why this change is linked to me.
I am going to try merging the Azure/vs17Dev into my branch to see if that helps... I did not touch that file.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@gucalder vs17Dev is not the current dev branch. psSdkJson6 is the current dev branch.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@gucalder Please revert Search-related changes

<ItemGroup>
<PackageReference Include="Microsoft.Azure.Management.ResourceManager" Version="1.5.0-preview" />
<ProjectReference Include="..\Management.Search\Management.Search.csproj" />
<ProjectReference Include="..\Management.Search\Microsoft.Azure.Management.Search.csproj" />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@gucalder Please revert Search-related changes

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.

4 participants