Hi team, I have a question regarding automation: Scenario: a visualization title is modified in our Test environment We would like to automate the following workflow: • Pull which visualizations have changed in our Test environment • Inspect changes in the visualization definition • Push the updated visualization to our Prod environment Current challenges: • To understand what has changed in our Test environment, currently it seems like our only option is to pull the entire workspace definition. This object is quite large and the ordering of keys is not consistent, which makes it hard to inspect/diff. • The nested structure generated by the CLI is friendlier, but we're not able to use this for a production workflow since it's still in beta What is the current recommended approach to handle this workflow? Thanks!

Hi Anant, can you please tell us a bit more about your Test environment? As I understand, you are working with our “GoodData Cloud” product, and there the Workspace Hierarchy is defined by the Parent-Child relations. More details on this can be found here: https://www.gooddata.com/docs/cloud/workspaces/workspace-hierarchy/

Hi @Michael Ullock, we have separate GoodData Cloud environments for Test and Prod. Each environment has a parent workspace which contains the LDM as well as dashboard and visualization definitions

Hello Anant, we have an article published on this HERE Also, there was a previous thread related in a similar fashion in using GitHub: https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1726168294406809 Could you please review this and let us know if it helps in your use case?

Thanks @Joseph Heun I'll review the article and the linked thread. It looks like some of this is still dependent on the GoodData CLI and VSCode extension - is there an ETA for when these will be out of beta? The

gooddata-dbt

package referenced the sample repo is also not accessible - is this still available?