Docs 22.1 Planning: Dry-run restore

Kathryn Hancox (kathancox) commented:

* *What is the purpose?*
** Provide users with a way to test a restore without restoring the full set of data. Use the {{dry_run}} option with {{RESTORE}}
** Likely to be two values ({{long}} and {{short}}) to describe the kind of dry run to be completed.
* *What are the deliverables?*
** Ensure there are no mentions of not being able to rename a database on restore. Or, edit these to reference the new option.
** Add {{dry_run}}to the options list on the {{RESTORE}} page. Along with a description of the different options.
** Add an example to the {{RESTORE}} demonstrating this option, and perhaps provide a description outlining the use case of this. For both {{long}} and {{short}}.
** Test examples to ensure instructions work as expected.
* *Will this be backported?*
TBD
* *What is out of scope?*
Will this be addressed later?
* *RACI chart*
Responsible - Kathryn H.
Accountable - Kathryn H.
Consulted - Michael Butler, Liv Lobo
*Informed* - Liv Lobo
* *Risk or dependencies*
The engineering work isn’t yet complete (March 2, 2022)
* *Additional resources*

Jira Issue: DOC-2796