[Rt-commit] rt branch 5.0/tracking-rt-configuration-doc-update created. rt-5.0.3-125-g582da5de0c

BPS Git Server git at git.bestpractical.com
Tue Oct 11 21:34:33 UTC 2022

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "rt".

The branch, 5.0/tracking-rt-configuration-doc-update has been created
        at  582da5de0c53ba49c28a2322bd757174c83c8743 (commit)

- Log -----------------------------------------------------------------
commit 582da5de0c53ba49c28a2322bd757174c83c8743
Author: Brian Conry <bconry at bestpractical.com>
Date:   Tue Oct 11 16:30:59 2022 -0500

    Note configuration needed to load JSON initialdata
    This change documents the necessity of configuration enabling the use of
    the JSON initialdata format so that someone following the instructions
    from tracking-rt-configuration.pod with the default configuration will
    be able to load the changes into their target.

diff --git a/docs/tracking-rt-configuration.pod b/docs/tracking-rt-configuration.pod
index 3d38a714c9..1fda4cf312 100644
--- a/docs/tracking-rt-configuration.pod
+++ b/docs/tracking-rt-configuration.pod
@@ -144,6 +144,11 @@ and the new scrip we created:
+In order to apply the changes.json initialdata to your an RT
+you will need to add thee following to your configuration:
+    Set( $InitialdataFormatHandlers, [ 'RT::Initialdata::JSON' ] );
 You can now apply the changes.json initialdata to your production RT:
     sbin/rt-setup-database --action insert --datafile new/changes.json



More information about the rt-commit mailing list