Closed mansueli closed 1 year ago
This is most likely because you put inputs in the wrong order postgres://postgres:${{ inputs.supabase_url }}@${{ inputs.supabase_password }}
, password should be ahead of url 😂. It's correct in the full workflow, which is why it works correctly.
Additionally, we should use supabase_url
as the whole argument for -d
, previously it was actually used as supabase_host
, not the database url that contains the full information to connect to the database. This aligns the naming and functionality, and also solves the problem if someone uses a port other than the hard-coded 6543
.
Right now it is only possible to use secrets when using the full workflow directly i.e:
If you try to use it just with the GitHub actions, then it fails:
Error: