Gazer 0.2.14 - dashboard exported then imported across environments ends up in space with wrong id about gzr

[jakebanks]

I should say, modifying the space id referred to in MyDashboard.json didn't change its target.

[jakebanks]

As a workaround, I've been uploading the dashboards to the new environment into the space with the space id they came from, then moving them to the appropriate space. I hit a situation where the space ID doesn't exist in the new environment, and it threw this:

Error creating dashboard({
 <snip>
  "folder_id": 81,
  "space_id": "58"
 <snip>
})

Note that space id 58 is what I passed as an argument, but folder id 81 is the space they were downloaded from.

Doing a find and replace of "folder_id": 81 and replacing it with "folder_id": 58 got it to work!

Thanks

[drstrangelooker]

The latest versions of gzr remove the conflicting folder_id. The attributes folder_id and space_id are synonyms. We basically decided to rename the attribute. But when both are provided looker uses the folder_id rather than the space_id.

[jakebanks]

Thanks @deangelo-llooker