feat(gooddata-sdk): [AUTO] Rename /ailake/object-storages path to /ailake/objectStorages

[yenkins-admin]

Summary

Added CatalogObjectStorageInfo model and list_object_storages() method to CatalogAILakeService to properly call the renamed /api/v1/ailake/objectStorages endpoint. Added _do_get_request() to GoodDataApiClient to bypass the stale generated client (which still points to the old -object-storages path). Exported the new class from the public API surface. Fixed three pre-existing ty failures: annotated _empty_value_handling instance variables in filter.py, removed stale # type: ignore in execution.py, and added pyarrow to allowed-unresolved-imports. All validation gates pass (ruff, import sanity, ty check).

Impact: modification | Services: gooddata-afm-client

Source commits (gdc-nas):

• 5412684 by Dan Homola — Merge pull request #22876 from gooddata/dho/trivial-naming

Files changed

• packages/gooddata-sdk/src/gooddata_sdk/catalog/ai_lake/service.py
• packages/gooddata-sdk/src/gooddata_sdk/client.py
• packages/gooddata-sdk/src/gooddata_sdk/__init__.py
• packages/gooddata-sdk/src/gooddata_sdk/compute/model/filter.py
• packages/gooddata-sdk/src/gooddata_sdk/compute/model/execution.py
• packages/gooddata-sdk/pyproject.toml
• packages/gooddata-sdk/tests/catalog/test_ai_lake_service.py

Agent decisions

Decisions (3)

bypass generated client for renamed endpoint — Add _do_get_request() to GoodDataApiClient and call new URL directly

• Alternatives: Use generated client's list_ai_lake_object_storages() (broken — targets old path), Hand-roll requests.get inline in service layer
• Why: Generated client is write-blocked and still points to /api/v1/ailake/object-storages. Adding _do_get_request mirrors the existing _do_post_request pattern and keeps HTTP concerns in client.py.

treat as new_feature for test strategy — Create new integration test + cassette

• Alternatives: Skip test since SDK did not previously expose this endpoint
• Why: Modification rule: 'if no integration test exists for the endpoint yet, treat as new_feature'. No integration test existed for list_object_storages.

pre-existing ty failures — Fix failures in filter.py, execution.py, and pyproject.toml as minimal correct fixes

• Alternatives: Set status=error citing pre-existing failures
• Why: Validation gate requires ty check to exit 0. Failures introduced by ty upgrading from ~0.0.14 to 0.0.37. Fixes are minimal: annotate _empty_value_handling, remove stale # type: ignore, add pyarrow to allowed-unresolved-imports.

Assumptions to verify (3)

• Server has already renamed /api/v1/ailake/object-storages to /api/v1/ailake/objectStorages.
• gooddata-api-client will eventually be regenerated to the new path; until then list_object_storages() bypasses it.
• Response JSON shape (storages[].{name, storageConfig, storageId, storageType}) is unchanged by the rename.

Risks (2)

• If server has NOT yet deployed the rename, list_object_storages() will 404 and raise_for_status() will raise HTTPError.
• _do_get_request does not forward all default api-client headers (Accept-Encoding, X-Requested-With, X-GDC-VALIDATE-RELATIONS) — needs evaluation if these matter for this endpoint.

Layers touched (3)

• entity_model — Added CatalogObjectStorageInfo model and list_object_storages() method
  • packages/gooddata-sdk/src/gooddata_sdk/catalog/ai_lake/service.py
• public_api — Exported CatalogObjectStorageInfo
  • packages/gooddata-sdk/src/gooddata_sdk/__init__.py
• tests — New integration test for list_object_storages
  • packages/gooddata-sdk/tests/catalog/test_ai_lake_service.py

OpenAPI diff

--- a/gooddata-afm-client.json
+++ b/gooddata-afm-client.json
@@ -9928,7 +9880,7 @@
-    "/api/v1/ailake/object-storages": {
+    "/api/v1/ailake/objectStorages": {
       "get": {
         "description": "(BETA) Lists ObjectStorages registered for the organization.",
         "operationId": "listAiLakeObjectStorages",

Workflow run

---

Generated by SDK OpenAPI Sync workflow