Uploaded image for project: 'R10K'
  1. R10K
  2. RK-305

Add --force (and --no-force) flags to "deploy" action.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • 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.

      Description

      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.

      https://github.com/puppetlabs/r10k/issues/483

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              anderson Anderson Mills
              Reporter:
              anderson Anderson Mills
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support