Confused by rt-dump-database

RT Users
1

I’m try to use rt-dump-database to move RT configs between development and
production, but am confused by how it’s supposed to be used.

rt-dump-database takes an optional parameter to turn $LocalOnly on/off and
it is on by default. This means no ACLs get dumped. If I turn it off, then
it goes into an infinite loop, which is documented in the code.

What series of steps should be performed to use this correctly?

Also, I was running into problems with XML parsing errors. There were pretty
easily cleared up by converting rt-dump-database to product YAML format
instead of XML.

Thanks.

-Todd

2

I’m try to use rt-dump-database to move RT configs between
development and production, but am confused by how it’s supposed to
be used.

rt-dump-database takes an optional parameter to turn $LocalOnly on/
off and it is on by default. This means no ACLs get dumped. If I
turn it off, then it goes into an infinite loop, which is documented
in the code.

Wanna patch it?

What series of steps should be performed to use this correctly?

It’s primarily been used as a debugging tool and usually used for
dumping scrips and custom fields.

Also, I was running into problems with XML parsing errors. There
were pretty easily cleared up by converting rt-dump-database to
product YAML format instead of XML.

I believe there is/was a mode to use Data::Dumper instead of XMLm as
well.