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

Refactor post-deploy purging to include control-repo level content

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:
    • Acceptance Criteria:
      • Should be able to configure on/off
      • Off by default
      • Items on whitelist are not purged when purging is turned on.
      • Items are purged
    • Story Points:
      5
    • Sprint:
      CODEMGMT 2016-06-15, CODEMGMT 2016-06-29
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      r10k has learned how to purge unmanaged content at the "environment" level, see the documentation changes on the merged PR for more details:

      https://github.com/puppetlabs/r10k/pull/609/files#diff-959150f0f98da0d668120ed9574c0727
      Show
      r10k has learned how to purge unmanaged content at the "environment" level, see the documentation changes on the merged PR for more details: https://github.com/puppetlabs/r10k/pull/609/files#diff-959150f0f98da0d668120ed9574c0727

      Description

      Currently r10k purges unrecognized content in the moduledir and unrecognized environments in the environmentdir, but it does not purge unrecognized content in an environment outside of the moduledir. As we are introducing the concept of multiple moduledirs in RK-222, we will need a way to purge things at the control-repo level.

      This should probably be a configurable option with the default as "off" until the next major release.

      There should also be a configurable "whitelist" of files/globs to skip over when purging and we should make sure we don't purge the .r10k-deploy.json file.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jesse Jesse Scott
              Reporter:
              jesse Jesse Scott
              QA Contact:
              Zach Reichert
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support