This was originally opened by @sf2ne because we decided we can't just update the node heartbeat for every API that node creds are used. In the case of this /changes API, it is necessary for it to look at the creds to decide whether it should be updating the HB for the node or agbot.
Maybe there are scaling reasons we want the agent to be able to set option noheartbeat=true on the /orgs/{orgid}/changes route?? (Today, it updates lastHeartbeat on every call to /orgs/{orgid}/changes.)
This was originally opened by @sf2ne because we decided we can't just update the node heartbeat for every API that node creds are used. In the case of this /changes API, it is necessary for it to look at the creds to decide whether it should be updating the HB for the node or agbot.
Maybe there are scaling reasons we want the agent to be able to set option
noheartbeat=true
on the/orgs/{orgid}/changes
route?? (Today, it updateslastHeartbeat
on every call to/orgs/{orgid}/changes
.)