You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(config): add undocummented remote types to turbo.json schema (#9073)
### Description
There has been an undocumented `remoteCache` field in `turbo.json` for
quite awhile (at least since 1.10). This PR adds documentation for the
it.
### Testing Instructions
Added unit tests to verify that when these are set in `turbo.json` they
are respected in the built config.
Copy file name to clipboardexpand all lines: packages/turbo-types/schemas/schema.json
+16
Original file line number
Diff line number
Diff line change
@@ -171,6 +171,22 @@
171
171
"enabled": {
172
172
"type": "boolean",
173
173
"description": "Indicates if the remote cache is enabled. When `false`, Turborepo will disable all remote cache operations, even if the repo has a valid token. If true, remote caching is enabled, but still requires the user to login and link their repo to a remote cache. Documentation: https://turbo.build/repo/docs/core-concepts/remote-caching"
174
+
},
175
+
"preflight": {
176
+
"type": "boolean",
177
+
"description": "When enabled, any HTTP request will be preceded by an OPTIONS request to determine if the request is supported by the endpoint.\n\nDocumentation: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#preflighted_requests"
178
+
},
179
+
"apiUrl": {
180
+
"type": "string",
181
+
"description": "Set endpoint for API calls to the remote cache. Documentation: https://turbo.build/repo/docs/core-concepts/remote-caching#self-hosting"
182
+
},
183
+
"loginUrl": {
184
+
"type": "string",
185
+
"description": "Set endpoint for requesting tokens during `turbo login`. Documentation: https://turbo.build/repo/docs/core-concepts/remote-caching#self-hosting"
186
+
},
187
+
"timeout": {
188
+
"type": "number",
189
+
"description": "Sets a timeout for remote cache operations. Value is given in seconds and only whole values are accepted. If `0` is passed, then there is no timeout for any cache operations."
Copy file name to clipboardexpand all lines: packages/turbo-types/schemas/schema.v2.json
+16
Original file line number
Diff line number
Diff line change
@@ -171,6 +171,22 @@
171
171
"enabled": {
172
172
"type": "boolean",
173
173
"description": "Indicates if the remote cache is enabled. When `false`, Turborepo will disable all remote cache operations, even if the repo has a valid token. If true, remote caching is enabled, but still requires the user to login and link their repo to a remote cache. Documentation: https://turbo.build/repo/docs/core-concepts/remote-caching"
174
+
},
175
+
"preflight": {
176
+
"type": "boolean",
177
+
"description": "When enabled, any HTTP request will be preceded by an OPTIONS request to determine if the request is supported by the endpoint.\n\nDocumentation: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#preflighted_requests"
178
+
},
179
+
"apiUrl": {
180
+
"type": "string",
181
+
"description": "Set endpoint for API calls to the remote cache. Documentation: https://turbo.build/repo/docs/core-concepts/remote-caching#self-hosting"
182
+
},
183
+
"loginUrl": {
184
+
"type": "string",
185
+
"description": "Set endpoint for requesting tokens during `turbo login`. Documentation: https://turbo.build/repo/docs/core-concepts/remote-caching#self-hosting"
186
+
},
187
+
"timeout": {
188
+
"type": "number",
189
+
"description": "Sets a timeout for remote cache operations. Value is given in seconds and only whole values are accepted. If `0` is passed, then there is no timeout for any cache operations."
0 commit comments