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
Change #161 updated the way seeds work to upload to S3 and apply a schema instead of a create/insert, to support larger seed files. Unfortunately, that is a breaking change for me - I have several small seed files and no access to upload to S3.
Is there a way of toggling between the old and new behaviour? If not I can try and PR something in to do that
Could you do something to detect changes that increase the scope of necessary IAM permissions? Newer versions require IAM access to athena:GetWorkGroup #262 is another change that required new IAM permissions that I don't have in my regulated environment
The text was updated successfully, but these errors were encountered:
Change #161 updated the way seeds work to upload to S3 and apply a schema instead of a create/insert, to support larger seed files. Unfortunately, that is a breaking change for me - I have several small seed files and no access to upload to S3.
The text was updated successfully, but these errors were encountered: