I've been trying to hit the version endpoint on my Ory Network project like so but I'm just getting back a 404

➜  gists git:(main) ✗ curl -sL \
  --header "Authorization: Bearer $ORY_API_KEY" \
  https://$<http://PROJECT_SLUG.projects.oryapis.com/version|PROJECT_SLUG.projects.oryapis.com/version> | jq
{
  "error": {
    "code": "404",
    "details": {
      "ruleId": "6176b3cb"
    },
    "message": "Invalid path",
    "reason": "No resource found using the specified path.",
    "status": "Not Found"
  }
}

Is there something subtle I'm missing? I can hit other endpoints on that project, which is in "dev" mode.

The version endpoint is not exposed, and probably erroneously included in the SDK. What do you need this for?

I was having issues with the rust sdk (documented here) and was trying to debug whether it was a versioning issue (thinking that I was perhaps using the wrong version of the sdk)

The SDKs are fully generated at the moment, so unless the fix can be done via configuration of the rust open-api generator, it might be difficult to get even simple fixes done. What would the fix be?

This is the fix: https://github.com/ibeckermayer/client-rust/pull/1/files That field that I'm removing there is noted to be redundant and only there for compatibility with an ancient OpenAPI (3.0) whereas you guys are now on 7.12.0. So one option is to revise the OpenAPI spec and just get rid of that redundant field, since apparently OpenAPI's rust generator has a bug in handling this type of structure (see chunleng's comment). That would require releasing as a major version upgrade. Another option is to just add a sed command somewhere around here to patch the generated files.