Try to fix GCP deploy by adding timeseries_db to config toml (#587)

* add timeseries_db to config toml

* automatically update packer-id

* trigger packer

* automatically update packer-id

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Author: david-crespo

packer/omicron.toml

@@ -34,7 +34,6 @@ level = "info"
 # Example output to a terminal (with colors)
 mode = "stderr-terminal"
 
-# Example output to a file, appending if it already exists.
-#mode = "file"
-#path = "logs/server.log"
-#if_exists = "append"
+# Configuration for interacting with the timeseries database
+[timeseries_db]
+address = "[::1]:8123"

tools/create_gcp_instance.sh

@@ -41,7 +41,7 @@ retry 2 gcloud compute instances create "$INSTANCE_NAME" \
 	--description="Machine automatically generated from branch ${BRANCH_NAME} of the oxidecomputer/console git repo." \
 	--hostname="${INSTANCE_NAME}.internal.oxide.computer" \
 	--zone=$ZONE \
-	--image=packer-1641329647 \
+	--image=packer-1641331516 \
 	--maintenance-policy=TERMINATE \
 	--restart-on-failure \
 	--machine-type=$INSTANCE_TYPE \