Send the ID token when calling the Log Destinations endpoints.
This could use the access key instead, but right now it's not trivial to get access (hm...) to the access key within the SDK code, and Austen's work to move platform logic out of the Framework introduces some utilities to ease that.
At some point we need to go through all these SDK's uses of ID token and replace them wherever possible with access key, for headless/CI use. For now though, the API doesn't care whether it receives the ID token or access key, so we can go ahead with this.
Send the ID token when calling the Log Destinations endpoints.
This could use the access key instead, but right now it's not trivial to get access (hm...) to the access key within the SDK code, and Austen's work to move platform logic out of the Framework introduces some utilities to ease that.
At some point we need to go through all these SDK's uses of ID token and replace them wherever possible with access key, for headless/CI use. For now though, the API doesn't care whether it receives the ID token or access key, so we can go ahead with this.