vendor: update all dependencies

vendor/github.com/aws/aws-sdk-go/models/apis/xray/2016-04-12/api-2.json

@@ -345,7 +345,8 @@
         "EndTime":{"shape":"Timestamp"},
         "Edges":{"shape":"EdgeList"},
         "SummaryStatistics":{"shape":"ServiceStatistics"},
-        "DurationHistogram":{"shape":"Histogram"}
+        "DurationHistogram":{"shape":"Histogram"},
+        "ResponseTimeHistogram":{"shape":"Histogram"}
       }
     },
     "ServiceId":{

vendor/github.com/aws/aws-sdk-go/models/apis/xray/2016-04-12/docs-2.json

@@ -5,9 +5,9 @@
     "BatchGetTraces": "<p>Retrieves a list of traces specified by ID. Each trace is a collection of segment documents that originates from a single request. Use <code>GetTraceSummaries</code> to get a list of trace IDs.</p>",
     "GetServiceGraph": "<p>Retrieves a document that describes services that process incoming requests, and downstream services that they call as a result. Root services process incoming requests and make calls to downstream services. Root services are applications that use the AWS X-Ray SDK. Downstream services can be other applications, AWS resources, HTTP web APIs, or SQL databases.</p>",
     "GetTraceGraph": "<p>Retrieves a service graph for one or more specific trace IDs.</p>",
-    "GetTraceSummaries": "<p>Retrieves IDs and metadata for traces available for a specified time frame using an optional filter. To get the full traces, pass the trace IDs to <code>BatchGetTraces</code>.</p>",
+    "GetTraceSummaries": "<p>Retrieves IDs and metadata for traces available for a specified time frame using an optional filter. To get the full traces, pass the trace IDs to <code>BatchGetTraces</code>.</p> <p>A filter expression can target traced requests that hit specific service nodes or edges, have errors, or come from a known user. For example, the following filter expression targets traces that pass through <code>api.example.com</code>:</p> <p> <code>service(\"api.example.com\")</code> </p> <p>This filter expression finds traces that have an annotation named <code>account</code> with the value <code>12345</code>:</p> <p> <code>annotation.account = \"12345\"</code> </p> <p>For a full list of indexed fields and keywords that you can use in filter expressions, see <a href=\"http://docs.aws.amazon.com/xray/latest/devguide/xray-console-filters.html\">Using Filter Expressions</a> in the <i>AWS X-Ray Developer Guide</i>.</p>",
     "PutTelemetryRecords": "<p>Used by the AWS X-Ray daemon to upload telemetry.</p>",
-    "PutTraceSegments": "<p>Uploads segment documents to AWS X-Ray. The X-Ray SDK generates segment documents and sends them to the X-Ray daemon, which uploads them in batches. A segment document can be a completed segment, an in-progress segment, or an array of subsegments.</p>"
+    "PutTraceSegments": "<p>Uploads segment documents to AWS X-Ray. The X-Ray SDK generates segment documents and sends them to the X-Ray daemon, which uploads them in batches. A segment document can be a completed segment, an in-progress segment, or an array of subsegments.</p> <p>Segments must include the following fields. For the full segment document schema, see <a href=\"http://docs.aws.amazon.com/xray/latest/devguide/xray-api-segmentdocuments.html\">AWS X-Ray Segment Documents</a> in the <i>AWS X-Ray Developer Guide</i>.</p> <p class=\"title\"> <b>Required Segment Document Fields</b> </p> <ul> <li> <p> <code>name</code> - The name of the service that handled the request.</p> </li> <li> <p> <code>id</code> - A 64-bit identifier for the segment, unique among segments in the same trace, in 16 hexadecimal digits.</p> </li> <li> <p> <code>trace_id</code> - A unique identifier that connects all segments and subsegments originating from a single client request.</p> </li> <li> <p> <code>start_time</code> - Time the segment or subsegment was created, in floating point seconds in epoch time, accurate to milliseconds. For example, <code>1480615200.010</code> or <code>1.480615200010E9</code>.</p> </li> <li> <p> <code>end_time</code> - Time the segment or subsegment was closed. For example, <code>1480615200.090</code> or <code>1.480615200090E9</code>. Specify either an <code>end_time</code> or <code>in_progress</code>.</p> </li> <li> <p> <code>in_progress</code> - Set to <code>true</code> instead of specifying an <code>end_time</code> to record that a segment has been started, but is not complete. Send an in progress segment when your application receives a request that will take a long time to serve, to trace the fact that the request was received. When the response is sent, send the complete segment to overwrite the in-progress segment.</p> </li> </ul> <p>A <code>trace_id</code> consists of three numbers separated by hyphens. For example, 1-58406520-a006649127e371903a2de979. This includes:</p> <p class=\"title\"> <b>Trace ID Format</b> </p> <ul> <li> <p>The version number, i.e. <code>1</code>.</p> </li> <li> <p>The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM December 2nd, 2016 PST in epoch time is <code>1480615200</code> seconds, or <code>58406520</code> in hexadecimal.</p> </li> <li> <p>A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.</p> </li> </ul>"
   },
   "shapes": {
     "Alias": {
@@ -47,9 +47,9 @@
       }
     },
     "BackendConnectionErrors": {
-      "base": "<p></p>",
+      "base": "<p/>",
       "refs": {
-        "TelemetryRecord$BackendConnectionErrors": "<p></p>"
+        "TelemetryRecord$BackendConnectionErrors": "<p/>"
       }
     },
     "BatchGetTracesRequest": {
@@ -139,8 +139,9 @@
     "Histogram": {
       "base": null,
       "refs": {
-        "Edge$ResponseTimeHistogram": "<p>Histogram describing the prominence of response times on the edge.</p>",
-        "Service$DurationHistogram": "<p>Histogram mapping the spread of trace durations</p>"
+        "Edge$ResponseTimeHistogram": "<p>A histogram that maps the spread of client response times on an edge.</p>",
+        "Service$DurationHistogram": "<p>A histogram that maps the spread of service durations.</p>",
+        "Service$ResponseTimeHistogram": "<p>A histogram that maps the spread of service response times.</p>"
       }
     },
     "HistogramEntry": {
@@ -192,19 +193,19 @@
     "NullableInteger": {
       "base": null,
       "refs": {
-        "BackendConnectionErrors$TimeoutCount": "<p></p>",
-        "BackendConnectionErrors$ConnectionRefusedCount": "<p></p>",
-        "BackendConnectionErrors$HTTPCode4XXCount": "<p></p>",
-        "BackendConnectionErrors$HTTPCode5XXCount": "<p></p>",
-        "BackendConnectionErrors$UnknownHostCount": "<p></p>",
-        "BackendConnectionErrors$OtherCount": "<p></p>",
+        "BackendConnectionErrors$TimeoutCount": "<p/>",
+        "BackendConnectionErrors$ConnectionRefusedCount": "<p/>",
+        "BackendConnectionErrors$HTTPCode4XXCount": "<p/>",
+        "BackendConnectionErrors$HTTPCode5XXCount": "<p/>",
+        "BackendConnectionErrors$UnknownHostCount": "<p/>",
+        "BackendConnectionErrors$OtherCount": "<p/>",
         "Edge$ReferenceId": "<p>Identifier of the edge. Unique within a service map.</p>",
         "Http$HttpStatus": "<p>The response status.</p>",
         "Service$ReferenceId": "<p>Identifier for the service. Unique within the service map.</p>",
-        "TelemetryRecord$SegmentsReceivedCount": "<p></p>",
-        "TelemetryRecord$SegmentsSentCount": "<p></p>",
-        "TelemetryRecord$SegmentsSpilloverCount": "<p></p>",
-        "TelemetryRecord$SegmentsRejectedCount": "<p></p>"
+        "TelemetryRecord$SegmentsReceivedCount": "<p/>",
+        "TelemetryRecord$SegmentsSentCount": "<p/>",
+        "TelemetryRecord$SegmentsSpilloverCount": "<p/>",
+        "TelemetryRecord$SegmentsRejectedCount": "<p/>"
       }
     },
     "NullableLong": {
@@ -243,7 +244,7 @@
       }
     },
     "Segment": {
-      "base": "<p>Information about a segment</p>",
+      "base": "<p>A segment from a trace that has been ingested by the X-Ray service. The segment can be compiled from documents uploaded with <a>PutTraceSegments</a>, or an <code>inferred</code> segment for a downstream service, generated from a subsegment sent by the service that called it.</p>",
       "refs": {
         "SegmentList$member": null
       }
@@ -251,7 +252,7 @@
     "SegmentDocument": {
       "base": null,
       "refs": {
-        "Segment$Document": "<p>The segment document.</p>"
+        "Segment$Document": "<p>The segment document</p>"
       }
     },
     "SegmentId": {
@@ -273,7 +274,7 @@
       }
     },
     "ServiceId": {
-      "base": "<p></p>",
+      "base": "<p/>",
       "refs": {
         "ServiceIds$member": null
       }
@@ -297,7 +298,7 @@
       "base": null,
       "refs": {
         "Service$Names": "<p>A list of names for the service, including the canonical name.</p>",
-        "ServiceId$Names": "<p></p>"
+        "ServiceId$Names": "<p/>"
       }
     },
     "ServiceStatistics": {
@@ -325,16 +326,16 @@
         "Http$HttpMethod": "<p>The request method.</p>",
         "Http$UserAgent": "<p>The request's user agent string.</p>",
         "Http$ClientIp": "<p>The IP address of the requestor.</p>",
-        "PutTelemetryRecordsRequest$EC2InstanceId": "<p></p>",
-        "PutTelemetryRecordsRequest$Hostname": "<p></p>",
-        "PutTelemetryRecordsRequest$ResourceARN": "<p></p>",
+        "PutTelemetryRecordsRequest$EC2InstanceId": "<p/>",
+        "PutTelemetryRecordsRequest$Hostname": "<p/>",
+        "PutTelemetryRecordsRequest$ResourceARN": "<p/>",
         "Service$Name": "<p>The canonical name of the service.</p>",
         "Service$AccountId": "<p>Identifier of the AWS account in which the service runs.</p>",
         "Service$Type": "<p>The type of service.</p> <ul> <li> <p>AWS Resource - The type of an AWS resource. For example, <code>AWS::EC2::Instance</code> for a application running on Amazon EC2 or <code>AWS::DynamoDB::Table</code> for an Amazon DynamoDB table that the application used.</p> </li> <li> <p>AWS Service - The type of an AWS service. For example, <code>AWS::DynamoDB</code> for downstream calls to Amazon DynamoDB that didn't target a specific table.</p> </li> <li> <p> <code>client</code> - Represents the clients that sent requests to a root service.</p> </li> <li> <p> <code>remote</code> - A downstream service of indeterminate type.</p> </li> </ul>",
         "Service$State": "<p>The service's state.</p>",
-        "ServiceId$Name": "<p></p>",
-        "ServiceId$AccountId": "<p></p>",
-        "ServiceId$Type": "<p></p>",
+        "ServiceId$Name": "<p/>",
+        "ServiceId$AccountId": "<p/>",
+        "ServiceId$Type": "<p/>",
         "ServiceNames$member": null,
         "TraceUser$UserName": "<p>The user's name.</p>",
         "UnprocessedTraceSegment$Id": "<p>The segment's ID.</p>",
@@ -343,7 +344,7 @@
       }
     },
     "TelemetryRecord": {
-      "base": "<p></p>",
+      "base": "<p/>",
       "refs": {
         "TelemetryRecordList$member": null
       }
@@ -351,7 +352,7 @@
     "TelemetryRecordList": {
       "base": null,
       "refs": {
-        "PutTelemetryRecordsRequest$TelemetryRecords": "<p></p>"
+        "PutTelemetryRecordsRequest$TelemetryRecords": "<p/>"
       }
     },
     "ThrottledException": {
@@ -373,7 +374,7 @@
         "GetTraceSummariesResult$ApproximateTime": "<p>The start time of this page of results.</p>",
         "Service$StartTime": "<p>The start time of the first segment that the service generated.</p>",
         "Service$EndTime": "<p>The end time of the last segment that the service generated.</p>",
-        "TelemetryRecord$Timestamp": "<p></p>"
+        "TelemetryRecord$Timestamp": "<p/>"
       }
     },
     "Trace": {
@@ -413,7 +414,7 @@
     "TraceSegmentDocumentList": {
       "base": null,
       "refs": {
-        "PutTraceSegmentsRequest$TraceSegmentDocuments": "<p>A JSON document defining one or more segments or subsegments. Segments must include the following fields.</p> <p class=\"title\"> <b>Required Segment Document Fields</b> </p> <ul> <li> <p> <code>name</code> - The name of the service that handled the request.</p> </li> <li> <p> <code>id</code> - A 64-bit identifier for the segment, unique among segments in the same trace, in 16 hexadecimal digits.</p> </li> <li> <p> <code>trace_id</code> - A unique identifier that connects all segments and subsegments originating from a single client request.</p> </li> <li> <p> <code>start_time</code> - Time the segment or subsegment was created, in floating point seconds in epoch time, accurate to milliseconds. For example, <code>1480615200.010</code> or <code>1.480615200010E9</code>.</p> </li> <li> <p> <code>end_time</code> - Time the segment or subsegment was closed. For example, <code>1480615200.090</code> or <code>1.480615200090E9</code>. Specify either an <code>end_time</code> or <code>in_progress</code>.</p> </li> <li> <p> <code>in_progress</code> - Set to <code>true</code> instead of specifying an <code>end_time</code> to record that a segment has been started, but is not complete. Send an in progress segment when your application receives a request that will take a long time to serve, to trace the fact that the request was received. When the response is sent, send the complete segment to overwrite the in-progress segment.</p> </li> </ul> <p>A <code>trace_id</code> consists of three numbers separated by hyphens. For example, 1-58406520-a006649127e371903a2de979. This includes:</p> <p class=\"title\"> <b>Trace ID Format</b> </p> <ul> <li> <p>The version number, i.e. <code>1</code>.</p> </li> <li> <p>The time of the original request, in Unix epoch time, in 8 hexadecimal digits. For example, 10:00AM December 2nd, 2016 PST in epoch time is <code>1480615200</code> seconds, or <code>58406520</code> in hexadecimal.</p> </li> <li> <p>A 96-bit identifier for the trace, globally unique, in 24 hexadecimal digits.</p> </li> </ul>"
+        "PutTraceSegmentsRequest$TraceSegmentDocuments": "<p>A string containing a JSON document defining one or more segments or subsegments.</p>"
       }
     },
     "TraceSummary": {

vendor/github.com/aws/aws-sdk-go/models/apis/xray/2016-04-12/paginators-1.json

@@ -0,0 +1,4 @@
+{
+  "pagination": {
+  }
+}