-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
versioning should be 1.0.0
Please rename VersionPrefix
with Version
<PackageReleaseNotes>This is a preview release of the Application Insights Data SDK.</PackageReleaseNotes> | ||
</PropertyGroup> | ||
<PropertyGroup> | ||
<TargetFrameworks>net452;netstandard1.4</TargetFrameworks> | ||
<RootNamespace>Microsoft.Azure.ApplicationInsights</RootNamespace> | ||
<RootNamespace>Microsoft.Azure.ApplicationInsights.Query</RootNamespace> | ||
<Version>1.0.0-Preview-1</Version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
<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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the spec merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's an open PR which changes an enum to modelAsString. Rest of the changes are merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good apart from the one comment
@@ -14,7 +14,9 @@ | |||
</ItemGroup> | |||
<ItemGroup> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please replace VersionPrefix
with Version
Also add <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
to the same PropertyGroup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
*.csproj
andAssemblyInfo.cs
files have been updated with the new version of the SDK.