allez apply¶
Apply local items to the branch workspace: one fab import per item, then a fab api read-back that proves each one landed. Items are the <Name>.<Type>/ folders on disk; the folders in git are the list of items. Each item gets its own pass/fail line. A failed import or a failed verification exits non-zero.
Not a promotion mechanism
allez apply is for development in a branch workspace. It reads neither config.yml nor parameter.yml, so items land exactly as authored. Moving a solution between environments is allez deploy, a different mechanism.
Usage¶
Arguments¶
| Argument | Description |
|---|---|
PATH |
Solution root (fabric/) or a single workspace sub-folder. Default: . |
Options¶
| Option | Description |
|---|---|
--item, -i <str> |
Apply only these items, by name or Name.Type. Repeatable. |
--verify-run |
After verifying, run each item via fab job run and wait until it finishes. |
--run-timeout <int> |
Seconds to allow each --verify-run job before giving up. |
--plan |
Preview without importing anything. |
Examples¶
allez apply fabric/reporting --plan # preview
allez apply fabric/reporting # every item in the sub-folder
allez apply fabric/reporting --item Report.Report # one item (repeatable)
allez apply fabric/data --verify-run --run-timeout 600 # apply, then run it until it finishes
Behaviour¶
- Never deletes. Removing an item folder from the repo does not unpublish it. Only
allez deploy's unpublish does. --verify-runreports separately. A failed run exits non-zero without hiding that the apply itself succeeded. It runs every selected item, so pair it with-i. A Warehouse or Report has no job to run, so it reports a failed run.- A SQL database cannot be applied.
fab importsends no definition format, so Fabric expects a dacpac and refuses the folder. The item reports as failed; publish it with apublish_sqlprojstep in a deploy instead. - Branch workspace only. There is no
--env. - Protected branches are refused (
protected-branches).