Define "relations" API as a sub-resource of cases and bookmarks. Allows users to define and maintain relationships between cases and bookmarks across various user scenarios

[ctoma73]

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:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[openapi-sdkautomation]

In Testing, Please Ignore

[Logs] (Generated from 5621d33, Iteration 8)

.NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]

• No packages generated.

Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]

• preview/securityinsight/mgmt/2017-08-01-preview [Logs] [Instructions] [Generation PR]
  • preview.securityinsight.mgmt.2017-08-01-preview.zip

Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]

• No packages generated.

JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]

• No packages generated.

[AutorestCI]

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#7275

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#5803

[majastrz]

I added some comments - please take a look.

[majastrz]

The biggest issue was the PUT vs GET. Given that the API is in PROD already and we're fairly late in the process, I will approve on the condition that we address this later. The easiest option I think is to return the target and source node properties in the PUT response and in the GETs. That should comply with the existing rules and also be a simple fix (hopefully).

[lirenhe]

@ctoma73 , please resolve the conflicts of the PR otherwise I am unable to merge it.

[ctoma73]

I merged and resolved all conflicts on branch. Please allow check in #Resolved

[ctoma73]

I’ve resolved all conflicts and merged the master branch. Please merge my PR! Thanks ! Claudiu

Sent from my iPhone

On Sep 17, 2019, at 8:03 PM, Renhe Li ***@***.***> wrote: @ctoma73 , please resolve the conflicts of the PR otherwise I am unable to merge it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

#Resolved

[ctoma73]

Asking please unblock merging and help merge this PR ? All comments and merge conflicts are resolved, please unblock merge! Thanks ! Any help appreciated! #Closed

[majastrz]

Asking please unblock merging and help merge this PR ? All comments and merge conflicts are resolved, please unblock merge! Thanks ! Any help appreciated! #Resolved

The assignee from the SDK team (on this PR, it's @lirenhe) has permissions to merge the PR. #Closed

[majastrz]

@lirenhe, I resolved the comments in CodeFlow, but we shouldn't require that. Once ARM team puts the ARMSignedOff label on a PR, it's good to go from our side.