Comments
1 comment
-
Official commentHello Benjamin,
Thank you for raising the issue with us, I would anticipate a failure to access a warehouse to possibly be an account level permissions issue rather than the script itself.
Are you using the same credentials in both instances please?
If you're willing to share the code we can also attempt to replicate the issue.
Add comment
Please sign in to leave a comment.
I have a script which creates a task in snowflake. All other scripts work fine, but this one fails with snowflake reporting that the warehouse specified in the statement does not exist.
I then run flyway with -X to see the exact sql sent. I copy it, and then run it directly in snowflake’s web ui in a worksheet that is set to use the same user, db, role and warehouse that flyway is using, and it runs without any issues.
Any ideas on what the difference would be? I know flyway uses jdbc, but I dont see how it could be any different.
I have flyway connect using a PAT I generated for my user and tied to the role I run flyway under, and that works for all the other scripts.
Any help appreciated on what could cause the issue
Using a fairly recent version of flyway container to run everything.