On this page
Kater CLI Explore and try ideas brainstorm
kater brainstorm copy
Copies a workspace into a topic of your brainstorm folder, so you can change the copy freely.
Then compare it with the original, and apply it when you like the result. It writes only in your brainstorm folder.
Examples
# Go to the snowflake_prod_connection connectioncd connections/snowflake_prod_connection# Copy the ad_reporting workspace into the promote_roas topic of your brainstorm folderkater brainstorm copy workspaces/ad_reporting --topic promote_roas# Compare the copy with its original, query by querykater compare --left workspaces/ad_reporting --right users/you@example.com/brainstorm/promote_roas/workspaces/ad_reporting# See what applying the copy would write, and write nothingkater workspace apply users/you@example.com/brainstorm/promote_roas/workspaces/ad_reporting --dry-runArguments
Options
It also takes the global options --json, --kater-root, --scope and --help.
What the copy holds
- A real workspace. Nothing outside your brainstorm folder reads it.
copied-from.yamlnames the original, and each file’s revision in the original and in the copy. - Apps stay behind. The original’s apps stay with it. Its
default-inputs.jsoncomes along, changed to name the copy’s queries. When none of its entries names a query of the copy, it stays behind. - It compiles once. The copy is saved even when it does not compile. The answer gives the copy’s path, how many files it copied, and that compile’s errors, by file.
--jsonreturns theworkspaceoperation’s answer, whosecopy_ofholds them. - Names. A name that the topic already has is refused, never numbered.
After the copy
kater brainstorm show on the copy lists each file it changed since it was copied. kater compare checks that its queries give the answers you expect. kater workspace apply writes its changes to the original.