Update policy for replacement of managed files
This commit is contained in:
@@ -510,7 +510,7 @@ Transfer fields and accepted values:
|
||||
- `transfer.on_destination_newer`: `skip`, `replace`, or `fail`. Default: `skip`.
|
||||
- `transfer.on_conflict`: `fail` or `replace`. Default: `fail`.
|
||||
|
||||
`replace` for `on_destination_newer` and `on_conflict` is honored only when `run --force` is supplied. There is no config field that enables forced replacement by default.
|
||||
`replace` for `on_destination_newer` and `on_conflict` applies only to valid distributor-managed destination state. Unmanaged destination content and invalid destination state still require the explicit `run --force` workflow where supported.
|
||||
|
||||
## Size And Duration Values
|
||||
|
||||
|
||||
Reference in New Issue
Block a user