Conversation
|
@bganapa and @deathly809 |
|
@sumitabarahmand After your spec PR has been merged please regenerate from merged spec. |
dsgouda
left a comment
There was a problem hiding this comment.
When ready, please squash commits into a single commit
There was a problem hiding this comment.
Please update PackageReleaseNotes
There was a problem hiding this comment.
please mention that repair api is supported only on AzureStack 1811 +
There was a problem hiding this comment.
@dsgouda can we add a checklist item in the PR saying 'I have updated relevant package release notes' ?
There was a problem hiding this comment.
I see that you already mention about 1811 :)
|
@dsgouda GitHub has the option of squashing the commits when you are merging the PR. We are ok for you to do this. Pls lets us know if you still want us to manually squash the commits |
|
@bganapa we lately started seeing issue with merges when we use squash/merge options, especially while trying to merge into other branches. |
|
Yes, we will squash the commits and update this PR once the specs PR is merged Azure/azure-rest-api-specs#4084 |
|
@sumitabarahmand Your REST spec has been merged, please regenerate and make requested changes above. Thanks! |
|
@azuresdkci retest this please |
|
@sumitabarahmand could you please squash the commits.. |
73cc042 to
6f95e42
Compare
fix build issues Add SDK unit test for Alert Repair rabase and resolve conflicts revert generate changes update SDK based on updated alert spec remove auto generated metadata update assembly version generate SDK with latest spec add autogenerated spec metadata generate SDK from merged specs update release notes
8c57f1e to
6b0c5f6
Compare
| Preview release of the InfrastructureInsights administrator SDK which allows administrators | ||
| 1) View the health of their AzureStack stamp resources | ||
| 2) View and manage alerts | ||
| Repair API is supported in azurestack 1811+ |
There was a problem hiding this comment.
nit: please stick to numbering scheme
There was a problem hiding this comment.
@dsgouda Should we only put in new things for release notes?
There was a problem hiding this comment.
Ideally yes, that way users know what changed from the last version
There was a problem hiding this comment.
Just updated the PR.
| /// <param name="closedByUserAlias">User alias who closed the | ||
| /// alert.</param> | ||
| public Alert(string id = default(string), string name = default(string), string type = default(string), IDictionary<string, string> tags = default(IDictionary<string, string>), string location = default(string), string closedTimestamp = default(string), string createdTimestamp = default(string), IList<IDictionary<string, string>> description = default(IList<IDictionary<string, string>>), string faultId = default(string), string alertId = default(string), string faultTypeId = default(string), string lastUpdatedTimestamp = default(string), IDictionary<string, string> alertProperties = default(IDictionary<string, string>), IList<IDictionary<string, string>> remediation = default(IList<IDictionary<string, string>>), string resourceRegistrationId = default(string), string resourceProviderRegistrationId = default(string), string severity = default(string), string state = default(string), string title = default(string), string impactedResourceId = default(string), string impactedResourceDisplayName = default(string), string closedByUserAlias = default(string)) | ||
| /// <param name="hasValidRemediationAction">Indicates if the alert can |
There was a problem hiding this comment.
Was this autogenerated or hand edited?
There was a problem hiding this comment.
Autogenerated
|
Will merge on CIs passing |
Description
SDK changes for the new Alert Repair admin operation
PR for the spec: Azure/azure-rest-api-specs#4084
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.