[RK-305] Add --force (and --no-force) flags to "deploy" action. - Puppet Tickets

XML

Word

Printable

Template:
customfield_10700 219780
Acceptance Criteria:
- The r10k actions "deploy environment" should respect --no-force flags to not overwrite local modifications will.
- The default for "deploy environment" should be --force.
Team:
Enterprise in the Cloud
Story Points:
0
Sprint:
ETC 2017-11-14, ETC 2017-11-28, ETC 2017-12-12

Release Notes:
Known Issue
Release Notes Summary:
r10k deploy now has a --no-force flag to prevent overwriting local modifications in git-based modules.

We changed the default behavior when encountering local modifications in 2.4.0 but we should really have flags to opt in or out of the behavior.

I think it's reasonable for the deploy default to be --force.

All the functionality already exists, it should just be a matter of plumbing through the new flags.

clones

RK-264 Add --force (and --no-force) flags to "puppetfile install" action.

relates to

RK-265 "puppetfile install" action overwrites local modifications