supabase-add

Author: SaxonF

cmd/add.go

@@ -0,0 +1,27 @@
+package cmd
+
+import (
+	"github.com/spf13/afero"
+	"github.com/spf13/cobra"
+	"github.com/supabase/cli/internal/add"
+)
+
+var (
+	templateInputs []string
+
+	addCmd = &cobra.Command{
+		GroupID: groupLocalDev,
+		Use:     "add <template-url-or-path>",
+		Short:   "Add a template package to your project",
+		Args:    cobra.ExactArgs(1),
+		RunE: func(cmd *cobra.Command, args []string) error {
+			return add.Run(cmd.Context(), args[0], templateInputs, afero.NewOsFs())
+		},
+	}
+)
+
+func init() {
+	flags := addCmd.Flags()
+	flags.StringArrayVarP(&templateInputs, "input", "i", []string{}, "Set template input values as key=value.")
+	rootCmd.AddCommand(addCmd)
+}

docs/supabase/db/pull.md

@@ -9,3 +9,5 @@ Requires your local project to be linked to a remote database by running `supaba
 Optionally, a new row can be inserted into the migration history table to reflect the current state of the remote database.
 
 If no entries exist in the migration history table, `pg_dump` will be used to capture all contents of the remote schemas you have created. Otherwise, this command will only diff schema changes against the remote database, similar to running `db diff --linked`.
+
+When using `--experimental`, SQL objects are written as declarative schema files. You can customize where new schema files are written via `[db.migrations.schema_placement]` in `supabase/config.toml`, while `[db.migrations].schema_paths` still controls execution order.