-
Notifications
You must be signed in to change notification settings - Fork 0
/
.tailcallrc.graphql
805 lines (789 loc) · 25.3 KB
/
.tailcallrc.graphql
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
"""
The @addField operator simplifies data structures and queries by adding a field that
inlines or flattens a nested field or node within your schema. more info [here](https://tailcall.run/docs/guides/operators/#addfield)
"""
directive @addField(
"""
Name of the new field to be added
"""
name: String!
"""
Path of the data where the field should point to
"""
path: [String!]
) repeatable on OBJECT
"""
The @cache operator enables caching for the query, field or type it is applied to.
"""
directive @cache(
"""
Specifies the duration, in milliseconds, of how long the value has to be stored in
the cache.
"""
maxAge: Int!
) on OBJECT | FIELD_DEFINITION
"""
Provides the ability to refer to multiple fields in the Query or Mutation root.
"""
directive @call(
"""
Steps are composed together to form a call. If you have multiple steps, the output
of the previous step is passed as input to the next step.
"""
steps: [Step]
) on FIELD_DEFINITION
"""
The `@expr` operators allows you to specify an expression that can evaluate to a
value. The expression can be a static value or built form a Mustache template. schema.
"""
directive @expr(
body: JSON
) on FIELD_DEFINITION
"""
The @graphQL operator allows to specify GraphQL API server request to fetch data
from.
"""
directive @graphQL(
"""
Named arguments for the requested field. More info [here](https://tailcall.run/docs/guides/operators/#args)
"""
args: [KeyValue]
"""
This refers to the base URL of the API. If not specified, the default base URL is
the one specified in the `@upstream` operator.
"""
baseURL: String
"""
If the upstream GraphQL server supports request batching, you can specify the 'batch'
argument to batch several requests into a single batch request.Make sure you have
also specified batch settings to the `@upstream` and to the `@graphQL` operator.
"""
batch: Boolean!
"""
The headers parameter allows you to customize the headers of the GraphQL request
made by the `@graphQL` operator. It is used by specifying a key-value map of header
names and their values.
"""
headers: [KeyValue]
"""
Specifies the root field on the upstream to request data from. This maps a field
in your schema to a field in the upstream schema. When a query is received for this
field, Tailcall requests data from the corresponding upstream field.
"""
name: String!
) on FIELD_DEFINITION
"""
The @grpc operator indicates that a field or node is backed by a gRPC API.For instance,
if you add the @grpc operator to the `users` field of the Query type with a service
argument of `NewsService` and method argument of `GetAllNews`, it signifies that
the `users` field is backed by a gRPC API. The `service` argument specifies the name
of the gRPC service. The `method` argument specifies the name of the gRPC method.
In this scenario, the GraphQL server will make a gRPC request to the gRPC endpoint
specified when the `users` field is queried.
"""
directive @grpc(
"""
This refers to the base URL of the API. If not specified, the default base URL is
the one specified in the `@upstream` operator.
"""
baseURL: String
"""
The key path in the response which should be used to group multiple requests. For
instance `["news","id"]`. For more details please refer out [n + 1 guide](https://tailcall.run/docs/guides/n+1#solving-using-batching).
"""
batchKey: [String!]
"""
This refers to the arguments of your gRPC call. You can pass it as a static object
or use Mustache template for dynamic parameters. These parameters will be added in
the body in `protobuf` format.
"""
body: String
"""
The `headers` parameter allows you to customize the headers of the HTTP request made
by the `@grpc` operator. It is used by specifying a key-value map of header names
and their values. Note: content-type is automatically set to application/grpc
"""
headers: [KeyValue]
"""
This refers to the gRPC method you're going to call. For instance `GetAllNews`.
"""
method: String!
) on FIELD_DEFINITION
"""
The @http operator indicates that a field or node is backed by a REST API.For instance,
if you add the @http operator to the `users` field of the Query type with a path
argument of `"/users"`, it signifies that the `users` field is backed by a REST API.
The path argument specifies the path of the REST API. In this scenario, the GraphQL
server will make a GET request to the API endpoint specified when the `users` field
is queried.
"""
directive @http(
"""
This refers to the base URL of the API. If not specified, the default base URL is
the one specified in the `@upstream` operator.
"""
baseURL: String
"""
The `batchKey` parameter groups multiple data requests into a single call. For more
details please refer out [n + 1 guide](https://tailcall.run/docs/guides/n+1#solving-using-batching).
"""
batchKey: [String!]
"""
The body of the API call. It's used for methods like POST or PUT that send data to
the server. You can pass it as a static object or use a Mustache template to substitute
variables from the GraphQL variables.
"""
body: String
"""
The `encoding` parameter specifies the encoding of the request body. It can be `ApplicationJson`
or `ApplicationXWwwFormUrlEncoded`. @default `ApplicationJson`.
"""
encoding: Encoding
"""
The `headers` parameter allows you to customize the headers of the HTTP request made
by the `@http` operator. It is used by specifying a key-value map of header names
and their values.
"""
headers: [KeyValue]
"""
Schema of the input of the API call. It is automatically inferred in most cases.
"""
input: Schema
"""
This refers to the HTTP method of the API call. Commonly used methods include `GET`,
`POST`, `PUT`, `DELETE` etc. @default `GET`.
"""
method: Method
"""
Schema of the output of the API call. It is automatically inferred in most cases.
"""
output: Schema
"""
This refers to the API endpoint you're going to call. For instance `https://jsonplaceholder.typicode.com/users`.For
dynamic segments in your API endpoint, use Mustache templates for variable substitution.
For instance, to fetch a specific user, use `/users/{{args.id}}`.
"""
path: String!
"""
This represents the query parameters of your API call. You can pass it as a static
object or use Mustache template for dynamic parameters. These parameters will be
added to the URL.
"""
query: [KeyValue]
) on FIELD_DEFINITION
directive @js(
script: String!
) on FIELD_DEFINITION
"""
The @link directive allows you to import external resources, such as configuration
– which will be merged into the config importing it –, or a .proto file – which
will be later used by `@grpc` directive –.
"""
directive @link(
"""
The id of the link. It is used to reference the link in the schema.
"""
id: String
"""
The source of the link. It can be a URL or a path to a file. If a path is provided,
it is relative to the file that imports the link.
"""
src: String!
"""
The type of the link. It can be `Config`, or `Protobuf`.
"""
type: LinkType
) repeatable on SCHEMA
directive @modify(
name: String
omit: Boolean
) on FIELD_DEFINITION
"""
Used to omit a field from public consumption.
"""
directive @omit on FIELD_DEFINITION
directive @protected on OBJECT | FIELD_DEFINITION
"""
The `@server` directive, when applied at the schema level, offers a comprehensive
set of server configurations. It dictates how the server behaves and helps tune tailcall
for various use-cases.
"""
directive @server(
"""
`apolloTracing` exposes GraphQL query performance data, including execution time
of queries and individual resolvers.
"""
apolloTracing: Boolean
"""
`batchRequests` combines multiple requests into one, improving performance but potentially
introducing latency and complicating debugging. Use judiciously. @default `false`.
"""
batchRequests: Boolean
"""
`globalResponseTimeout` sets the maximum query duration before termination, acting
as a safeguard against long-running queries.
"""
globalResponseTimeout: Int
"""
`headers` contains key-value pairs that are included as default headers in server
responses, allowing for consistent header management across all responses.
"""
headers: Headers
"""
`hostname` sets the server hostname.
"""
hostname: String
"""
`introspection` allows clients to fetch schema information directly, aiding tools
and applications in understanding available types, fields, and operations. @default
`true`.
"""
introspection: Boolean
"""
`pipelineFlush` allows to control flushing behavior of the server pipeline.
"""
pipelineFlush: Boolean
"""
`port` sets the Tailcall running port. @default `8000`.
"""
port: Int
"""
`queryValidation` checks incoming GraphQL queries against the schema, preventing
errors from invalid queries. Can be disabled for performance. @default `false`.
"""
queryValidation: Boolean
"""
`responseValidation` Tailcall automatically validates responses from upstream services
using inferred schema. @default `false`.
"""
responseValidation: Boolean
"""
A link to an external JS file that listens on every HTTP request response event.
"""
script: ScriptOptions
"""
`showcase` enables the /showcase/graphql endpoint.
"""
showcase: Boolean
"""
This configuration defines local variables for server operations. Useful for storing
constant configurations, secrets, or shared information.
"""
vars: [KeyValue]
"""
`version` sets the HTTP version for the server. Options are `HTTP1` and `HTTP2`.
@default `HTTP1`.
"""
version: HttpVersion
"""
`workers` sets the number of worker threads. @default the number of system cores.
"""
workers: Int
) on SCHEMA
"""
Used to represent an identifier for a type. Typically used via only by the configuration
generators to provide additional information about the type.
"""
directive @tag(
"""
A unique identifier for the type.
"""
id: String!
) on OBJECT
"""
The @telemetry directive facilitates seamless integration with OpenTelemetry, enhancing
the observability of your GraphQL services powered by Tailcall. By leveraging this
directive, developers gain access to valuable insights into the performance and behavior
of their applications.
"""
directive @telemetry(
export: TelemetryExporter
"""
The list of headers that will be sent as additional attributes to telemetry exporters
Be careful about **leaking sensitive information** from requests when enabling the
headers that may contain sensitive data
"""
requestHeaders: [String!]
) on SCHEMA
"""
The `upstream` directive allows you to control various aspects of the upstream server
connection. This includes settings like connection timeouts, keep-alive intervals,
and more. If not specified, default values are used.
"""
directive @upstream(
"""
`allowedHeaders` defines the HTTP headers allowed to be forwarded to upstream services.
If not set, no headers are forwarded, enhancing security but possibly limiting data
flow.
"""
allowedHeaders: [String!]
"""
This refers to the default base URL for your APIs. If it's not explicitly mentioned
in the `@upstream` operator, then each [@http](#http) operator must specify its own
`baseURL`. If neither `@upstream` nor [@http](#http) provides a `baseURL`, it results
in a compilation error.
"""
baseURL: String
"""
An object that specifies the batch settings, including `maxSize` (the maximum size
of the batch), `delay` (the delay in milliseconds between each batch), and `headers`
(an array of HTTP headers to be included in the batch).
"""
batch: Batch
"""
The time in seconds that the connection will wait for a response before timing out.
"""
connectTimeout: Int
"""
When set to `true`, it will ensure no HTTP, GRPC, or any other IO call is made more
than once within the context of a single GraphQL request.
"""
dedupe: Boolean
"""
The `http2Only` setting allows you to specify whether the client should always issue
HTTP2 requests, without checking if the server supports it or not. By default it
is set to `false` for all HTTP requests made by the server, but is automatically
set to true for GRPC.
"""
http2Only: Boolean
"""
Providing httpCache size enables Tailcall's HTTP caching, adhering to the [HTTP Caching
RFC](https://tools.ietf.org/html/rfc7234), to enhance performance by minimizing redundant
data fetches. Defaults to `0` if unspecified.
"""
httpCache: Int
"""
The time in seconds between each keep-alive message sent to maintain the connection.
"""
keepAliveInterval: Int
"""
The time in seconds that the connection will wait for a keep-alive message before
closing.
"""
keepAliveTimeout: Int
"""
A boolean value that determines whether keep-alive messages should be sent while
the connection is idle.
"""
keepAliveWhileIdle: Boolean
"""
The time in seconds that the connection pool will wait before closing idle connections.
"""
poolIdleTimeout: Int
"""
The maximum number of idle connections that will be maintained per host.
"""
poolMaxIdlePerHost: Int
"""
The `proxy` setting defines an intermediary server through which the upstream requests
will be routed before reaching their intended endpoint. By specifying a proxy URL,
you introduce an additional layer, enabling custom routing and security policies.
"""
proxy: Proxy
"""
The time in seconds between each TCP keep-alive message sent to maintain the connection.
"""
tcpKeepAlive: Int
"""
The maximum time in seconds that the connection will wait for a response.
"""
timeout: Int
"""
The User-Agent header value to be used in HTTP requests. @default `Tailcall/1.0`
"""
userAgent: String
) on SCHEMA
input Apollo {
"""
Setting `apiKey` for Apollo.
"""
apiKey: String!
"""
Setting `graphRef` for Apollo in the format <graphId>@<variant>.
"""
graphRef: String!
"""
Setting `platform` for Apollo.
"""
platform: String
"""
Setting `userVersion` for Apollo.
"""
userVersion: String
"""
Setting `version` for Apollo.
"""
version: String
}
input Batch {
delay: Int!
headers: [String!]
maxSize: Int
}
"""
The @cache operator enables caching for the query, field or type it is applied to.
"""
input Cache {
"""
Specifies the duration, in milliseconds, of how long the value has to be stored in
the cache.
"""
maxAge: Int!
}
"""
Type to configure Cross-Origin Resource Sharing (CORS) for a server.
"""
input Cors {
"""
Indicates whether the server allows credentials (e.g., cookies, authorization headers)
to be sent in cross-origin requests.
"""
allowCredentials: Boolean
"""
A list of allowed headers in cross-origin requests. This can be used to specify custom
headers that are allowed to be included in cross-origin requests.
"""
allowHeaders: [String!]
"""
A list of allowed HTTP methods in cross-origin requests. These methods specify the
actions that are permitted in cross-origin requests.
"""
allowMethods: [Method]
"""
A list of origins that are allowed to access the server's resources in cross-origin
requests. An origin can be a domain, a subdomain, or even 'null' for local file schemes.
"""
allowOrigins: [String!]
"""
Indicates whether requests from private network addresses are allowed in cross-origin
requests. Private network addresses typically include IP addresses reserved for internal
networks.
"""
allowPrivateNetwork: Boolean
"""
A list of headers that the server exposes to the browser in cross-origin responses.
Exposing certain headers allows the client-side code to access them in the response.
"""
exposeHeaders: [String!]
"""
The maximum time (in seconds) that the client should cache preflight OPTIONS requests
in order to avoid sending excessive requests to the server.
"""
maxAge: Int
"""
A list of header names that indicate the values of which might cause the server's
response to vary, potentially affecting caching.
"""
vary: [String!]
}
enum Encoding {
ApplicationJson
ApplicationXWwwFormUrlencoded
}
"""
The `@expr` operators allows you to specify an expression that can evaluate to a
value. The expression can be a static value or built form a Mustache template. schema.
"""
input Expr {
body: JSON
}
"""
The @graphQL operator allows to specify GraphQL API server request to fetch data
from.
"""
input GraphQL {
"""
Named arguments for the requested field. More info [here](https://tailcall.run/docs/guides/operators/#args)
"""
args: [KeyValue]
"""
This refers to the base URL of the API. If not specified, the default base URL is
the one specified in the `@upstream` operator.
"""
baseURL: String
"""
If the upstream GraphQL server supports request batching, you can specify the 'batch'
argument to batch several requests into a single batch request.Make sure you have
also specified batch settings to the `@upstream` and to the `@graphQL` operator.
"""
batch: Boolean!
"""
The headers parameter allows you to customize the headers of the GraphQL request
made by the `@graphQL` operator. It is used by specifying a key-value map of header
names and their values.
"""
headers: [KeyValue]
"""
Specifies the root field on the upstream to request data from. This maps a field
in your schema to a field in the upstream schema. When a query is received for this
field, Tailcall requests data from the corresponding upstream field.
"""
name: String!
}
"""
The @grpc operator indicates that a field or node is backed by a gRPC API.For instance,
if you add the @grpc operator to the `users` field of the Query type with a service
argument of `NewsService` and method argument of `GetAllNews`, it signifies that
the `users` field is backed by a gRPC API. The `service` argument specifies the name
of the gRPC service. The `method` argument specifies the name of the gRPC method.
In this scenario, the GraphQL server will make a gRPC request to the gRPC endpoint
specified when the `users` field is queried.
"""
input Grpc {
"""
This refers to the base URL of the API. If not specified, the default base URL is
the one specified in the `@upstream` operator.
"""
baseURL: String
"""
The key path in the response which should be used to group multiple requests. For
instance `["news","id"]`. For more details please refer out [n + 1 guide](https://tailcall.run/docs/guides/n+1#solving-using-batching).
"""
batchKey: [String!]
"""
This refers to the arguments of your gRPC call. You can pass it as a static object
or use Mustache template for dynamic parameters. These parameters will be added in
the body in `protobuf` format.
"""
body: String
"""
The `headers` parameter allows you to customize the headers of the HTTP request made
by the `@grpc` operator. It is used by specifying a key-value map of header names
and their values. Note: content-type is automatically set to application/grpc
"""
headers: [KeyValue]
"""
This refers to the gRPC method you're going to call. For instance `GetAllNews`.
"""
method: String!
}
input Headers {
"""
`cacheControl` sends `Cache-Control` headers in responses when activated. The `max-age`
value is the least of the values received from upstream services. @default `false`.
"""
cacheControl: Boolean
"""
`cors` allows Cross-Origin Resource Sharing (CORS) for a server.
"""
cors: Cors
"""
`headers` are key-value pairs included in every server response. Useful for setting
headers like `Access-Control-Allow-Origin` for cross-origin requests or additional
headers for downstream services.
"""
custom: [KeyValue]
"""
`experimental` allows the use of `X-*` experimental headers in the response. @default
`[]`.
"""
experimental: [String!]
"""
`setCookies` when enabled stores `set-cookie` headers and all the response will be
sent with the headers.
"""
setCookies: Boolean
}
"""
The @http operator indicates that a field or node is backed by a REST API.For instance,
if you add the @http operator to the `users` field of the Query type with a path
argument of `"/users"`, it signifies that the `users` field is backed by a REST API.
The path argument specifies the path of the REST API. In this scenario, the GraphQL
server will make a GET request to the API endpoint specified when the `users` field
is queried.
"""
input Http {
"""
This refers to the base URL of the API. If not specified, the default base URL is
the one specified in the `@upstream` operator.
"""
baseURL: String
"""
The `batchKey` parameter groups multiple data requests into a single call. For more
details please refer out [n + 1 guide](https://tailcall.run/docs/guides/n+1#solving-using-batching).
"""
batchKey: [String!]
"""
The body of the API call. It's used for methods like POST or PUT that send data to
the server. You can pass it as a static object or use a Mustache template to substitute
variables from the GraphQL variables.
"""
body: String
"""
The `encoding` parameter specifies the encoding of the request body. It can be `ApplicationJson`
or `ApplicationXWwwFormUrlEncoded`. @default `ApplicationJson`.
"""
encoding: Encoding
"""
The `headers` parameter allows you to customize the headers of the HTTP request made
by the `@http` operator. It is used by specifying a key-value map of header names
and their values.
"""
headers: [KeyValue]
"""
Schema of the input of the API call. It is automatically inferred in most cases.
"""
input: Schema
"""
This refers to the HTTP method of the API call. Commonly used methods include `GET`,
`POST`, `PUT`, `DELETE` etc. @default `GET`.
"""
method: Method
"""
Schema of the output of the API call. It is automatically inferred in most cases.
"""
output: Schema
"""
This refers to the API endpoint you're going to call. For instance `https://jsonplaceholder.typicode.com/users`.For
dynamic segments in your API endpoint, use Mustache templates for variable substitution.
For instance, to fetch a specific user, use `/users/{{args.id}}`.
"""
path: String!
"""
This represents the query parameters of your API call. You can pass it as a static
object or use Mustache template for dynamic parameters. These parameters will be
added to the URL.
"""
query: [KeyValue]
}
enum HttpVersion {
HTTP1
HTTP2
}
input JS {
script: String!
}
input KeyValue {
key: String!
value: String!
}
enum LinkType {
Config
Protobuf
Script
Cert
Key
Operation
Htpasswd
Jwks
Grpc
}
enum Method {
GET
POST
PUT
PATCH
DELETE
HEAD
OPTIONS
CONNECT
TRACE
}
input Modify {
name: String
omit: Boolean
}
"""
Output the opentelemetry data to otlp collector
"""
input OtlpExporter {
headers: [KeyValue]
url: String!
}
"""
Output the telemetry metrics data to prometheus server
"""
input PrometheusExporter {
format: PrometheusFormat
path: String!
}
"""
Output format for prometheus data
"""
enum PrometheusFormat {
text
protobuf
}
input Proxy {
url: String!
}
input ScriptOptions {
timeout: Int
}
"""
Output the opentelemetry data to the stdout. Mostly used for debug purposes
"""
input StdoutExporter {
"""
Output to stdout in pretty human-readable format
"""
pretty: Boolean!
}
"""
Provides the ability to refer to a field defined in the root Query or Mutation.
"""
input Step {
"""
The arguments that will override the actual arguments of the field.
"""
args: JSON
"""
The name of the field on the `Mutation` type that you want to call.
"""
mutation: String
"""
The name of the field on the `Query` type that you want to call.
"""
query: String
}
"""
The @telemetry directive facilitates seamless integration with OpenTelemetry, enhancing
the observability of your GraphQL services powered by Tailcall. By leveraging this
directive, developers gain access to valuable insights into the performance and behavior
of their applications.
"""
input Telemetry {
export: TelemetryExporter
"""
The list of headers that will be sent as additional attributes to telemetry exporters
Be careful about **leaking sensitive information** from requests when enabling the
headers that may contain sensitive data
"""
requestHeaders: [String!]
}
input TelemetryExporter {
stdout: StdoutExporter
otlp: OtlpExporter
prometheus: PrometheusExporter
apollo: Apollo
}
input Schema {
Obj: JSON
Arr: Schema
Opt: Schema
Enum: [String!]
}
"""
A date string, such as 2007-12-03, is compliant with the full-date format outlined in section 5.6 of the RFC 3339 (https://datatracker.ietf.org/doc/html/rfc3339) profile of the ISO 8601 standard for the representation of dates and times using the Gregorian calendar.
"""
scalar Date
"""
field whose value conforms to the standard internet email address format as specified in HTML Spec: https://html.spec.whatwg.org/multipage/input.html#valid-e-mail-address.
"""
scalar Email
"""
Empty scalar type represents an empty value.
"""
scalar Empty
"""
The JSON scalar type represents JSON values as specified by [ECMA-404](www.ecma-international.org/publications/files/ECMA-ST/ ECMA-404.pdf).
"""
scalar JSON
"""
A field whose value conforms to the standard E.164 format as specified in E.164 specification (https://en.wikipedia.org/wiki/E.164).
"""
scalar PhoneNumber
"""
A field whose value conforms to the standard URL format as specified in RFC3986 (https://www.ietf.org/rfc/rfc3986.txt), and it uses real JavaScript URL objects.
"""
scalar Url