-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Added monitor subnet to SapMonitor model #8915
Conversation
Azure Pipelines successfully started running 1 pipeline(s). |
Can one of the admins verify this patch? |
azure-sdk-for-java - Release
|
azure-sdk-for-js - Release
|
azure-cli-extensions - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-net - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Hi @PakDLiu could you please provide some information about the |
Yes, I added the new field: monitorSubnet. |
@@ -617,6 +617,10 @@ | |||
"readOnly": true, | |||
"type": "string", | |||
"description": "The version of the payload running in the Collector VM" | |||
}, | |||
"monitorSubnet": { |
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.
monitorSubnet [](start = 9, length = 13)
Is this property required?
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.
yes
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.
Then this is a breaking change that should be done in a new API version.
In reply to: 402059679 [](ancestors = 402059679)
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.
This is still a preview API version and the API is still in flux.
We also know that no one outside of our team is using this API yet.
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.
Got it. That's fine then.
In general, I would recommend working in a development branch in the public or private Swagger repo when the API is still in flux. What's in master
branch in this repo is considered public and available for use regardless of the -preview
suffix on the API version.
In reply to: 402062621 [](ancestors = 402062621)
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 see, thanks!
Will do that in the future
@@ -16,7 +16,8 @@ | |||
"enableCustomerAnalytics": true, | |||
"logAnalyticsWorkspaceArmId": "", | |||
"logAnalyticsWorkspaceId": "", | |||
"logAnalyticsWorkspaceSharedKey": "" | |||
"logAnalyticsWorkspaceSharedKey": "", |
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.
"" [](start = 42, length = 2)
Can you provide example resource IDs for all the properties that are being specified. ""
is not really helpful to users. (This comment applies to all examples and properties in the examples.)
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.
done
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 update examples to make them more meaningful, but the change looks good to me. Signed off from ARM side.
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @PakDLiu could you please resolve the CI failures? (Except the breaking change since it is acceptable for a preview API) then this will be good to merge, thanks |
Azure Pipelines successfully started running 1 pipeline(s). |
Didn't notice there were other errors. |
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 👍
Azure Pipelines successfully started running 1 pipeline(s). |
* Added monitor subnet to SapMonitor model * updated examples * Fixed JSON * fixed examples
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.