list_repository_objects
List design-time objects in a space via the Datasphere CLI, catching undeployed or unexposed items that catalog search misses. Get a complete inventory of a space's contents.
Instructions
List design-time objects in a space by reading the REPOSITORY through the Datasphere CLI — not the Catalog API. Use this when an object is expected but does not show up in search_catalog, get_space_assets or smart_query: those only see objects that are deployed AND exposed for consumption, while this tool also sees objects with @DataWarehouse.consumption.external: false. Also the right tool for a true inventory of what a space actually contains. Requires the CLI to be installed and logged in — check with datasphere_cli_status. Costs one CLI call per object type, so keep object_types narrow.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| top | No | Maximum results per object type (CLI default: 25) | |
| skip | No | Number of results to skip per object type, for pagination | |
| space_id | Yes | Space identifier (e.g., 'SAP_CONTENT', 'DIMITRITEST') | |
| object_types | No | CLI object types to list. Default: views, local-tables, analytic-models. Use ["all"] to sweep all 18 types (slow: one CLI call each). Valid: remote-tables, local-tables, er-models, views, analytic-models, task-chains, data-flows, replication-flows, transformation-flows, data-access-controls, business-entities, fact-models, consumption-models, intelligent-lookups, ontologies, contexts, types, services | |
| status_filter | No | Filter by deployment status, e.g. 'Deployed' or 'Changed' | |
| technical_names | No | Comma-separated technical names to look for, e.g. 'MY_VIEW,MY_TABLE'. The fastest way to answer 'does this object exist at all?' | |
| include_dependencies | No | Accepted for compatibility; the CLI list command returns no dependency data |