[App Insights/Operational Insights] Add GET /query operation, fix operationId inconsistency

[alexeldeib]

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• The title of the PR 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 information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[AutorestCI]

Automation for azure-sdk-for-python

A PR has been created for you:
Azure/azure-sdk-for-python#3234

[AutorestCI]

Automation for azure-sdk-for-node

A PR has been created for you:
Azure/azure-sdk-for-node#3466

[AutorestCI]

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

[AutorestCI]

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#2669

[azuresdkci]

Can one of the admins verify this patch?

[sergey-shandar]

The changes in stable API are potential SDK breaking changes

[alexeldeib]

I had been doing work to clean up the operation groups as part of a general effort towards stable/ v1.0.0 versions of the data plane SDKs (we have preview versions for C#, Node, Java, and Python). This isn't strictly necessary and I could revert it, but is in line with what I've done in the other api-versions/with App Insights as well.

[sergey-shandar]

@alexeldeib please, resolve this issue https://travis-ci.org/Azure/azure-rest-api-specs/jobs/422715930

[alexeldeib]

@sergey-shandar I fixed a few issues, OAV is failing to validate this line in the spec however, which I haven't changed in months:

https://travis-ci.org/Azure/azure-rest-api-specs/jobs/423166594#L651

azure-rest-api-specs/specification/applicationinsights/data-plane/microsoft.insights/preview/2018-04-20/swagger.json

Line 1081 in e850b4e

"@ai.messages": {

I think this is an issue with OAV though? The property is clearly defined, even if the validation can't see it. Could it be an issue parsing the @ in the key?

[sergey-shandar]

@alexeldeib yes, it's OAV issue. I will check if I can fix it.

[sergey-shandar]

@alexeldeib I will provide a fix for OAV to unblock the PR.

[sergey-shandar]

@alexeldeib I've fixed the semantic validation tool, it works now https://travis-ci.org/Azure/azure-rest-api-specs/builds/423166589?utm_source=github_status&utm_medium=notification

There are still model validation issues https://travis-ci.org/Azure/azure-rest-api-specs/jobs/423166602