[Endpoint] Add Endpoint Details route

[pzl]

Summary

Adds API route for getting a single Endpoint by ID

note: WIP, unit tests are missing. Functionality is otherwise there.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

---

Example:

curl -s -H 'kbn-xsrf: xxx' \
  --user elastic:changeme -H "Content-Type: application/json" \
  http://localhost:5601/api/endpoint/endpoints/57ec37ff-9318-4652-8efa-db615ef40779 \
   | jq .

{
  "@timestamp": 1580395815407,
  "event": {
    "created": "2020-01-30T14:50:15.407Z"
  },
  "endpoint": {
    "policy": {
      "id": "00000000-0000-0000-0000-000000000000"
    }
  },
  "agent": {
    "version": "6.2.5",
    "id": "89ea71c2-d461-4bd3-8de5-c95b75a54626"
  },
  "host": {
    "id": "57ec37ff-9318-4652-8efa-db615ef40779",
    "hostname": "gaspard-9.example.com",
    "ip": [
      "10.147.107.88"
    ],
    "mac": [
      "a2-ea-e7-60-13-8a",
      "88-a4-c9-30-15-2b",
      "8a-81-97-f9-2d-90"
    ],
    "architecture": "x86",
    "os": {
      "name": "windows 6.3",
      "full": "Windows Server 2012R2",
      "version": "6.3"
    }
  }
}

Response when not getting any results:

{
  "statusCode": 404,
  "error": "Not Found",
  "message": "Endpoint Not Found"
}

Resolves: elastic/endpoint-app-team#100

[kevinlog]

to get by the label checks:

only, put 7.7 instead of 7.6

The Team labels help us track.

Also, add [Endpoint] to the title at some point before merging

[nnamdifrankie]

Please can we add some simple api integration tests, we already have some data that can be used? Ideally we may want to create a different data set for the feature. But I think it is fine to add it to the already existing test. https://github.com/elastic/kibana/blob/master/x-pack/test/api_integration/apis/endpoint/endpoints.ts

[charlie-pichette]

@pzl can you add a test where an endpoint doesn't exist?

[pzl]

@charlie-pichette I believe this tests the case where the endpoint doesn't exist

[nnamdifrankie]

Do we all agree it should be 404, I think so going by what I have seen about REST the appropriate response is missing data should be 404.

[charlie-pichette]

@pzl what is 'BADID'? That seems to me to be a malformed id instead of an id that doesn't exist. If we are not doing any validation on the id, such as if it is supposed to be a UUID that is a valid UUID format, then this seems ok.

[charlie-pichette]

We are not doing any validation on the endpoint id being submitted. I'm fine with this test.

[charlie-pichette]

The tests are good.

[pzl]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 4a50a5c

History

• 💔 Build #23542 failed 7ecc524
• 💚 Build #23391 succeeded 2de4e1e
• 💔 Build #23366 failed 93a0d4b
• 💚 Build #22224 succeeded bed9b4943dfbdf972551d77e97e6cd2b122d239e

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kevinlog]

@pzl can you add "Feature:Endpoint" label? Also, we should start linking the original GitHub issue to the PR. Can you edit the original description and add "Resolves: https://github.com/elastic/endpoint-app-team/issues/100" ?