Speaking of the RT CLI tool, are there plans to extend its functionality
any? For example, how about adding the ability to set custom field
values? Or perhaps to specify a local file to add as an attachment to a
ticket…
Thanks,
Ryan Roland
Network & Security Administrator
Information Technology
Division of Recreational Sports
Indiana University
Speaking of the RT CLI tool, are there plans to extend its functionality
any? For example, how about adding the ability to set custom field
values? Or perhaps to specify a local file to add as an attachment to a
ticket…
Patches are most certainly welcome.
Best,
Jesse
Speaking of the RT CLI tool, are there plans to extend its functionality
any? For example, how about adding the ability to set custom field
values? Or perhaps to specify a local file to add as an attachment to a
ticket…Patches are most certainly welcome.
Jesse,
Do you have any documentation on the REST interface that you’ve
implemented? Or even the particular docs on REST (in general) that you
worked from?
Travis
Travis Campbell - Unix Systems Administrator = travis@mpdtxmail.amd.com
5900 E. Ben White Blvd, Austin, TX 78741 = travis.campbell@amd.com
TEL: (512) 602-1888 PAG: (512) 604-0341 = webmaster@mpdtxmail.amd.com
“Does anything work as expected?” Yes. An axe through the CPU.
Speaking of the RT CLI tool, are there plans to extend its functionality
any? For example, how about adding the ability to set custom field
values? Or perhaps to specify a local file to add as an attachment to a
ticket…Patches are most certainly welcome.
Jesse,
Do you have any documentation on the REST interface that you’ve
implemented?
Only as comments in the code.
Or even the particular docs on REST (in general) that you
worked from?
It’s basically that “GET” gets you the current version of a resource and
“POST” updates a resource. RT’s implementation uses RFC822 style
messages, though in the past couple years, XML has become the defacto
standard.