Django-pgclone

Feature

- Add ``pgclone copy`` command. [Wes Kendall, 6ad17b9]

The ``pgclone copy`` command is a shortcut for running ``CREATE DATABASE <target> TEMPLATE <source>``
for doing quick copies. This command complements local ``pgclone restore`` commands.

For example, copy the current database with ``pgclone copy``, and quickly restore it with
``pgclone restore :current``. Use a custom name with ``pgclone copy :custom_name`` and restore it
with ``pgclone restore :custom_name``.

Note that this command takes out an exclusive lock on the source database, meaning it should not be
executed in production environments.
- Add ``settings.PGCLONE_ALLOW_DUMP`` setting. [Wes Kendall, 82c90f4]

Set this setting to ``False`` to prevent the ability to run ``pgclone dump``.

Trivial

- Add ability to specify endpoint url [Jack Linke, 2e1e5f5]

Bug

- Quote database connection strings [Wesley Kendall, 31fd3cf]

Database connection strings are properly quoted to avoid issues when there
are special characters.

Trivial

- Updated developer utilities with the latest Django library template [Wesley Kendall, 2508920]

Trivial

- Implemented a more robust routing method for pre-swap hooks [Wes Kendall, 8f34c40]

Trivial

- Local development enhancements [Wes Kendall, 5d62570]
- Test against Django 4.1 and other CI improvements [Wes Kendall, c11c848]

Trivial

- Don't close original connection during routing [Wes Kendall, 93e5c03]

Bug

- Fix issue routing connections during restore [Wes Kendall, 2ab5552]

An issue was fixed that prevented routing hooks during restores from
functioning properly.