migrate

Use this plan to migrate data from Security Compliance Management 2.x. The plan installs a fresh instance of Security Compliance Management 3.x and allows you to migrate any 2.x data to the new install. For complete instructions on how to use this plan to migrate from 2.x to 3.x, see Migrate from Security Compliance Management 2.x to 3.x.

Usage

bolt plan run complyadm::migrate [offline=<value>] [skip_preflights=<value>]

Parameters

This plan accepts the following parameters:

ignore_failing_preflights: Optional parameter that when set to true ignores failed preflight checks, which are OS and hardware checks performed to make sure system requirements are met. Default: false
upload_images: Optional parameter that specifies where to pull images from. Set this to true to curl images locally from a public GCS bucket and then upload to the installation node. Set this to false to pull images directly from the registry on the installation node. Default: true

Was this page helpful?

We’re sorry to hear that!
Please tell us why so we can help. Enter your feedback and email. This form is sent to the Puppet docs team. We ask for your email as we might contact you regarding your feedback. If you need help with the product itself, visit Puppet Support or ask in Puppet Community on Slack. Feedback:

Email Address:

To learn about how Puppet uses your personal information, visit our privacy policy.

If you leave us your email, we may contact you regarding your feedback. For more information on how Puppet uses your personal information, see our privacy policy.

See an issue? Please file a JIRA ticket in our [DOCUMENTATION] project.