Kater CLI Share and administer admin connection
kater admin connection update
Changes a connection's settings, schemas or tables in its connection.yaml.
Only what you give changes, and Kater tests new warehouse settings before it saves them. It never changes modeling/, so run kater sync --resource-type db_dataset after you change the schemas or tables.
Examples
# Take a schema out of the connection's selectionkater admin connection update snowflake_prod_connection --remove-schema DEMO_DB.ANALYTICS_VELIR_GA4# Put the schema back in the selectionkater admin connection update snowflake_prod_connection --add-schema DEMO_DB.ANALYTICS_VELIR_GA4# Never sync one table of a schemakater admin connection update snowflake_prod_connection --exclude-table DEMO_DB.ANALYTICS_AD_REPORTING.AD_REPORTING__URL_REPORT# Sync that table againkater admin connection update snowflake_prod_connection --include-table DEMO_DB.ANALYTICS_AD_REPORTING.AD_REPORTING__URL_REPORT# Set a database's timezone and the query timeoutkater admin connection update snowflake_prod_connection --timezone DEMO_DB=America/Los_Angeles --query-timeout 600# Print the new connection.yaml, and save nothingkater admin connection update snowflake_prod_connection --label "Snowflake production" --dry-runArguments
Options
It also takes the global options --json, --kater-root, --scope and --help.
When you change warehouse settings
Kater tests the connection with the new settings before it saves them. When the test fails, nothing changes. Run kater admin connection test after a change to the credential on Kater’s server.
What it changes
- It rewrites only the lines that it changes, so the file keeps your comments.
- To rename a database or a schema, or to give one a
labelor adescription, edit the file. - It changes
connection.yamlin your local copy. Commit the change and runkater git pushto publish it. - You need edit access to the connection’s
connection.yaml.