Docs: OpenAPI spec incorrectly mentions teamId instead of slug about turbo

[chris-olszewski]

I just double checked and we currently don't make use of that endpoint so you will be fine not implementing it.

I will update the OpenAPI spec to omit that endpoint.

[chris-olszewski]

Apologies for the confusion, both teamId and slug are valid query params for specifying which team you are using. If you connect your repository though something like turbo link, then a team id will be saved and teamId will be used when accessing the remote cache. TURBO_TEAM uses the slug query parameter instead since it isn't a team id.

Looking into fixing this in the upstream OpenAPI spec.

[AdiRishi]

Hey @chris-olszewski , thanks for confirming this 😄
Looking forward to having this updated in the OpenAPI spec.

I had another question, I know this is off topic to the current issue, so happy to open a new one if you want.
I'm wondering if you could help explain what the POST /v8/artifacts route is supposed to do.
The docs say it has this input

{
  "hashes": [
    "string"
  ]
}

and gives this as an example for output

{
  "additionalProp1": {
    "size": 0,
    "taskDurationMs": 0,
    "tag": "string"
  },
  // ...
}

The output example is super unclear, I'm really not sure what data I'm meant to be returning here. What are the additionalProp keys? Is this saying that I have to echo the metadata even to the server via the /v8/artifacts/events endpoint?
Keen to get some clarity 🙏 . This is the last unimplemented endpoint I have left for my custom server.

[chris-olszewski]

OpenAPI spec has been updated to mention slug and teamId. Still working on fully removing the POST /v8/artifacts since it's unused.

[AdiRishi]

Thanks Chris.
I'm happy to close out this issue, or keep it open until your other changes are synced, whatever you'd like