You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have some mechanism for recording http requests and responses in starlark. There's a few levels at which this could work:
when developing a transform script, cache an http response and replay it on future runs, so that the destination site doesn't get hammered, and also doesn't send back different data that breaks in-progress code
record all http responses so that we maintain an audit trail and make transforms be fully reproducible
only record http responses as hashes or checksums, so we can at least tell users when something has changed. May need some kind of smart differ that ignores unimportant dynamic content
When caching http responses, we have a few ways to handle them:
Record the response, and freeze it during development, never hitting the server again
Set the timestamp when an http request is made, send the http header "If-Modified-Since", and upon receiving a 304 status code, supply the cached version
The text was updated successfully, but these errors were encountered:
We should have some mechanism for recording http requests and responses in starlark. There's a few levels at which this could work:
When caching http responses, we have a few ways to handle them:
The text was updated successfully, but these errors were encountered: