The checklist before anybody clicks

A refresh started without this is how a week of unreleased configuration disappears. The checklist is short and every line is there because somebody lost something. EXPORT FIRST. Configuration built in the target since the last refresh, as a configuration package. List the settings that packages do NOT capture — Lesson 5 — and record them by hand. Take a note of role assignments made in the target, which will be replaced by production's. TELL PEOPLE, AND TELL THEM WHAT THEY LOSE. Everybody with work in that environment: testers mid-cycle, anybody holding an open sandbox, anybody whose test data is about to vanish. "The environment will be refreshed on Saturday" is not enough — say "anything you have built or entered there since the last refresh will be gone", because that is the sentence that makes people act. VERIFY BEFORE, NOT AFTER. Confirm the export completed and can be opened.…

In this module: Module 16 · Environment management: P2T, refreshes and what breaks

1. 1The environments, and what each is for
2. 2What a P2T actually copies
3. 3The checklist before anybody clicksFree preview
4. 4Data masking and why it is not optional
5. 5Preserving configuration across a refresh
6. 6Integrations after a refresh
7. 7Scheduling refreshes around a project
8. 8What breaks: four refresh failures
9. 9Lab briefing · Plan a refresh you could defend