- Reference
- Version ยท 6.0
- Change Automation Reference
targeting-file
Last updated: September 29, 2026
Overrides the targeting file a policy checks command reads or writes. By default the file is derived from your checks settings file name, with the extension replaced by .targeting.yaml, so this parameter is optional on checks targeting add, list, and remove. On checks run it is what tells Liquibase to apply targeting at all.
Note: Omit it on checks run and no targeting rules are applied. The run succeeds and reports nothing about targeting, so a missing value looks like a clean run rather than an error.
Syntax
You can set this parameter in the following ways:
Option | Syntax |
Command CLI parameter |
|
Liquibase properties file (defaults file) |
|
Command flow file argument (example) |
|
JVM system property (JAVA_OPTS environment variable) |
|
Liquibase environment variable |
|
Replace <subcommand> with the policy check command you are configuring. This parameter applies to these commands:
runtargeting addtargeting listtargeting remove
A bare file name resolves next to the checks settings file's own directory. A path with its own directory is used exactly as given. For the file format and what each rule field means, see Checks targeting file.