Good day guys,
I'm experiencing a weird behaviour with the wsapi for user request, when calling from aws lambda with python requests library, not sure if anyone has experienced something similar or I've missed some checks/parameters
the url pattern im calling is
https://rally1.rallydev.com/slm/webservice/v2.0/user?workspace=https://rally1.rallydev.com/slm/webservice/v2.0/workspace/xxxxxx&query=&fetch=true&start=1&pagesize=20the respond I am getting is the user records but only limited fields:
{
"_rallyAPIMajor": "2",
"_rallyAPIMinor": "0",
"_ref": "https://rally1.rallydev.com/slm/webservice/v2.0/user/xxxx",
"_refObjectUUID": "someUUID",
"_objectVersion": "2387",
"_refObjectName": "xxxx xxxx",
"ObjectID": XXXX,
"CostCenter": "None",
"Department": "None",
"Disabled": true,
"DisplayName": "xxxx xxxx",
"EmailAddress": "xxxx@email.com",
"FirstName": "xxxx",
"LastName": "xxxx",
"MiddleName": null,
"OfficeLocation": "None",
"Phone": null,
"Role": "None",
"UserName": "username_xxxx",
"_type": "User"
}
- I checked I have the same url parameters as what is show in the api documentation, with the fetch full object query=&fetch=true
- when tested via the api documentation or postman, this works as expected and gives me a full list of fields with objects from other tables like subscription, projects and many other fields
- *this only happens when I call from lambda python with the `requests` and `urllib3` library, the only difference i can see so far is only the request's user-agent header
- *this only happens with the `user` request, other requests like project, workspace etc seems to be working fine when i do fetch=true
- could our account be throttled? anything else i need to check? is there a security parameter or header flag I need to set?
thanks and
kind regards
------------------------------
Ethan HO
Senior Analyst Engineer
NAB Australia
------------------------------