Bootstrapping usually refers to the starting of a self-sustaining process that is supposed to proceed without external input.
UUID and Revision are required to operate with Configuration Manager.
If you update to Dalet Flex 5.1.1 and above, and you have objects created in older versions of Dalet Flex, you should use bootstrapping in order to assign UUIDs to those objects, as they will not have UUIDs.
Whenever you start over with a new environment, it is recommended to bootstrap the live environment first, and reverse the configuration process to pre-live, UAT etc. Here, the live objects act as a source and other environments as a target.
Configuration Manager is used to execute this operation process. The process is
executed promoting backwards configuration, from the live or production environment, for example, to the previous working environments (e.g.: stage, QA, development, local user…)
These steps will take you through the Bootstrapping process:
- Prepare the process with a database backup.
- Open a new change request with the source and target pointing to the live environment:
`open --source <<source name>> --target <<target name>> --bootstrapping_type`
- Next you must bootstrap by ID:
`open --source <<source_name>> --target <<target_name>> --bootstrapping_type BOOTSTRAP_BY_ID`.
If you want to bootstrap using the same environment you must bootstrap by ID. On the other hand, if you were to bootstrap across multiple environments, you would add BOOTSTRAP_BY_NAME instead. E.g., You have an environment already bootstrapped (LIVE in 5.1.x), and you want to match the UUID to downward environments -UAT, QA, DEV...-.
- Pull all the objects from source environment that you intend to bootstrap (e.g. by type).
E.g., `pull --type action`
- Enter the `prepare-bootstrap` command, and the target will bootstrap the UUID and revision code for any objects that don’t have them. In this case, we'll bootstrap by object type (action).
E.g., `prepare-bootstrap --type action`
- Now update the Target environment by entering the bootstrap command.
- Note: In the context of bootstrapping, the bootstrap command replaces the commit command.
- When Configuration Manager asks you Please confirm that you want to bootstrap configurations on Target <Y,N>, type Y to confirm.
- Configuration Manager will then inform you that the "Commit was successful"
In order to find out which commands are available during a bootstrapping session, press the Tab key whilst in a change request.