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
When a local API is deployed that's using the live-reloading/multi-model caching feature and the specified model(s) is/are public, the API will stop abruptly if no AWS credentials have been configured for it (either via the local environment or by including the credentials in the .env file).
Suggested solution
If a model is public and there are no AWS credentials set, then the S3 client should be anonymous.
The text was updated successfully, but these errors were encountered:
Version
Since 0.22.
Description
When a local API is deployed that's using the live-reloading/multi-model caching feature and the specified model(s) is/are public, the API will stop abruptly if no AWS credentials have been configured for it (either via the local environment or by including the credentials in the
.env
file).Suggested solution
If a model is public and there are no AWS credentials set, then the S3 client should be anonymous.
The text was updated successfully, but these errors were encountered: