[App Insights] Sync to swagger, bump to 1.0.0-preview-1, rename package *breaking changes*#4790
Conversation
|
I've been refining the data plane swagger for Application Insights and working towards 1.0.0 release for all of our SDKs. This PR rolls up a few changes I've made:
Adding on to that, this is an SDK to query data plane information -- metrics, logs and events for Azure resources. Application Insights also has numerous clients for sending telemetry to Azure, e.g. Microsoft.ApplicationInsights. I've made the relevant code changes already, but I wanted to ask how to go about this procedurally? Is there a precedent for package rename? Could we e.g., leave a note on the Microsoft.Azure.ApplicationInsights package page with a deprecation notice pointing to the newly named package? Would love to get thoughts on this. Thanks! |
Incomplete
|
| <AssemblyName>Microsoft.Azure.ApplicationInsights</AssemblyName> | ||
| <PackageId>Microsoft.Azure.ApplicationInsights</PackageId> | ||
| <PackageTags>Management.ApplicationInsights;</PackageTags> | ||
| <VersionPrefix>1.0.0.0</VersionPrefix> |
There was a problem hiding this comment.
versioning should be 1.0.0
Please rename VersionPrefix with Version
| <TargetFrameworks>net452;netstandard1.4</TargetFrameworks> | ||
| <RootNamespace>Microsoft.Azure.ApplicationInsights</RootNamespace> | ||
| <RootNamespace>Microsoft.Azure.ApplicationInsights.Query</RootNamespace> | ||
| <Version>1.0.0-Preview-1</Version> |
| <PackageId>Microsoft.Azure.ApplicationInsights</PackageId> | ||
| <PackageTags>Management.ApplicationInsights;</PackageTags> | ||
| <VersionPrefix>1.0.0.0</VersionPrefix> | ||
| <VersionSuffix>Preview-1</VersionSuffix> |
There was a problem hiding this comment.
Please remove this
Also, is the package stable or preview?
If this is still preview, the version can be bumped to 0.10.0-preview instead
| GitHub user: Azure | ||
| Branch: master | ||
| Commit: d122af3086f0b1693b9c506befc497a1f4a8b8e1 | ||
| GitHub user: alexeldeib |
There was a problem hiding this comment.
There's an open PR which changes an enum to modelAsString. Rest of the changes are merged.
There was a problem hiding this comment.
I can regenerate after it's merged. The same PR contains the namespace change.
|
@alexeldeib As such you cannot rename a package, we can hide/deprecate the old package with a message that redirects to a new package and then publish whichever new packages are needed. Please start an email thread if you need further details |
|
@dsgouda confirming, for preview version you want 0.10.0-preview not 1.0.0-preview? I made it 0.10.0-preview currently. |
|
@alexeldeib there should be a strong reason for major version bumps (if the REST spec version is new or if breaking changes are introduced to a stable version) |
dsgouda
left a comment
There was a problem hiding this comment.
Looks good apart from the one comment
| @@ -14,7 +14,9 @@ | |||
| </ItemGroup> | |||
| <ItemGroup> | |||
There was a problem hiding this comment.
Please replace VersionPrefix with Version
Also add <TreatWarningsAsErrors>true</TreatWarningsAsErrors> to the same PropertyGroup
dsgouda
left a comment
There was a problem hiding this comment.
LGTM subject to CIs passing
|
@dsgouda Bump since CI is green? |
Description
Azure/azure-rest-api-specs#3771
Azure/azure-rest-api-specs#3084 --> big one
Azure/azure-rest-api-specs#3385
Azure/azure-rest-api-specs#3997
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Testing Guidelines
SDK Generation Guidelines
*.csprojandAssemblyInfo.csfiles have been updated with the new version of the SDK.