Fighting with modified REST behavior in RT 4.2.2+

Hi all,
I have some external code that relies on REST to identify the relation
between users and groups in our RT.

Since RT 4.2.2, REST responses have changed and I am now trying to fix
the code but I have been unsuccesfull until now.

In the attachment you find the REST queries with the corresponding the
responses, both for RT v2.4.1 and for RT v4.2.2.

I would like to know if there is a way to recover the info I need.

Thank you in advance
Bye
Cris

REST_Calls_RT_anonymized_.txt (2.28 KB)

Hi all,
I have some external code that relies on REST to identify the relation
between users and groups in our RT.

Since RT 4.2.2, REST responses have changed and I am now trying to fix
the code but I have been unsuccesfull until now.

In the attachment you find the REST queries with the corresponding the
responses, both for RT v2.4.1 and for RT v4.2.2.

I would like to know if there is a way to recover the info I need.

Tell it what you want

./bin/rt show group/DBA -f members

This is likely a result of the refactoring and the fact that the
default members output doesn’t actually round trip (you can’t just
send back the member list to update it).

-kevin