tb push <path...>

Push files to Tinybird

Arguments

NameDescription
pathfolders, filepaths

Options

NameDescription
--prefix <text>Use prefix for all the resources
--dry-runRun the command without creating resources on the Tinybird account or any side effect
--checkEnable/Disable output checking, enabled by default
--no-checkEnable/Disable output checking, enabled by default
--push-depsPush dependencies, disabled by default
--debugPrints internal representation, can be combined with any command to get more information
-f, --forceOverride pipes when they already exist
--override-datasourceWhen pushing a pipe with a Materialized node if the target Data Source exists it will try to override it
--populatePopulate materialized nodes when pushing them
--subset <float>Populate with a subset percent of the data (limited to a maximum of 2M rows), this is useful to quickly test a materialized node with some data. The subset must be greater than 0 and lower than 0.1. A subset of 0.1 means a 10 percent of the data in the source Data Source will be used to populate the materialized view. Use it together with --populate, it has precedence over --sql-condition
--sql-condition <text>Populate with a SQL condition to be applied to the trigger Data Source of the Materialized View. For instance, `--sql-condition='date == toYYYYMM(now())'` it'll populate taking all the rows from the trigger Data Source which `date` is the current month. Use it together with --populate. --sql-condition is not taken into account if the --subset param is present. Including in the ``sql_condition`` any column present in the Data Source ``engine_sorting_key`` will make the populate job process less data
--unlink-on-populate-errorIf the populate job fails the Materialized View is unlinked and new data won't be ingested in the Materialized View. First time a populate job fails, the Materialized View is always unlinked
--fixturesAppend fixtures to data sources
--waitTo be used along with --populate command. Waits for populate jobs to finish, showing a progress bar. Disabled by default
--yesDo not ask for confirmation
--only-response-timesChecks only response times, when --force push a pipe
--workspace_map <text> <text>
  • Repeatable ♾
--workspace <text> <text>
  • Repeatable ♾
--no-versionsWhen set, resource dependency versions are not used, it pushes the dependencies as-is
--timeout <float>Timeout you want to use for the job populate
-l, --limit <integer range>Number of requests to validate
--sample-by-params <integer range>When set, we will aggregate the pipe_stats_rt requests by extractURLParameterNames(assumeNotNull(url)) and for each combination we will take a sample of N requests
-ff, --failfastWhen set, the checker will exit as soon one test fails
--ignore-orderWhen set, the checker will ignore the order of list properties
--validate-processed-bytesWhen set, the checker will validate that the new version doesn't process more than 25% than the current version
--last-requests-from-mainWhen set, the checker will get top requests requests from main
--helpShow this message and exit