Hi, We're using the GoodData CLI (

gd deploy

,

gd clone

) to manage and deploy analytical objects to our workspaces. We have a parent workspace with multiple child workspaces and we're trying to set up a backup solution that includes child workspace assets. Our current setup: • We use

gd deploy -p prod

to deploy. • Child workspaces inherit from the parent What we're trying to achieve: Back up all analytical objects (dashboards, metrics, visualizations) from both the parent and child workspaces • The backup should be in a format that's ready to redeploy via

gd deploy

if needed What we've tried:

gd clone

works great for the parent workspace but doesn't support pulling from child workspaces. • Fetching via the REST API works but produces a different schema than what

gd deploy

expects, so we can't use it directly for restore Questions: Is there a recommended way to back up child workspaces in a deploy-ready format?

There is no first‑class, deploy‑ready backup flow for child workspaces with the GoodData CLI today. From the Slack thread about

gd cli

and VS Code, GoodData confirms that: • CLI / VS Code currently work on a single workspace only and do not cover hierarchies or child workspaces. [CLI & VS Code limits] • For parent–child setups and workspace data filters, the Python SDK and APIs are the recommended approach instead of CLI. [CLI & VS Code limits] So, there is no supported way today to produce child‑workspace backups in the exact

gd deploy

YAML format. What is recommended for full, restorable backups (including children): 1. Use declarative / backup tools instead of CLI for backup/restore: ◦ Declarative Workspace API to back up and restore individual workspaces or all workspaces. [Workspace declarative API; Org backups] ◦ Or GoodData Pipelines / productivity tools: ▪︎

BackupManager.backup_hierarchies(...)

to back up a parent and all its child workspaces. [Pipelines backup hierarchies] ▪︎

gd-workspace-backup

/

gd-workspace-restore

scripts from

gooddata-productivity-tools

to back up and restore LDM, analytics model, UDFs, filter views, automations; they support: •

list-of-parents

→ backup full hierarchies •

entire-organization

→ backup all workspaces [GD Workspace Backup; GD Workspace Restore] These backups are deploy‑ready for restore via the same tools / declarative APIs, but not in

gd deploy

YAML structure. 2. Implication for your setup ◦ Continue using

gd deploy

for development / CI on the parent workspace. ◦ For disaster recovery / full backup including children, use: ▪︎ Python Pipelines

BackupManager.backup_hierarchies(workspace_ids=[parent_id])

, or ▪︎

python scripts/backup.py parents.csv conf.yaml -t list-of-parents

from productivity tools. [Pipelines backup hierarchies; GD Workspace Backup] Restore would then be done via the corresponding restore tool, not via

gd deploy

. [GD Workspace Restore] Because the knowledge sources explicitly state that CLI/VS Code do not yet support hierarchies, there is no documented way to get child‑workspace content into the same YAML schema that

gd deploy

expects. Any conversion between declarative JSON/YAML and

gd deploy

layout would have to be custom and is not described in the docs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Hi Pouyan, as it is mentioned, unfortunately, GoodData CLI does not support hierarchies. And the provided suggestion are the closest we have for your use case. Please let us know if you have any further question.