Matt
Matt
My workaround workflow so far had been to copy the SQL preview and manually replace `NULL` with ``. Right click on cell to "Insert Empty String" solves this for me.
I created a PR to support multiple instances. https://github.com/mattes/gce-cloudsql-proxy-action/pull/5/files I think you should be able to use the PR like this: `uses: mattes/gce-cloudsql-proxy-action@multi-instances` Didn't test the code. Let me know...
I'd be surprised if the beta version changed, but it's a possibility. Can you try to use the [SDK to list your instance groups](https://cloud.google.com/sdk/gcloud/reference/compute/instance-groups/managed/list)? ``` gcloud beta compute instance-groups managed...
This is great, thanks! The project is still using the legacy Gopck.lock files. We can remove them, including vendor directory. I'll do a combined PR for some more cleanup.
I think there is more that needs to be done when setting up a database, i.e. roles and permissions. I'm unsure about this PR. I believe creating the database in...
Interesting. I don't think we have tests for this. I think we would need to implement this.
In that case, ALTER can't be wrapped in a transaction. migrate won't wrap any SQL commands. so that should be fine?
I don't think introducing custom markup is a good idea. But I'm always happy to discuss. https://github.com/mattes/migrate/blob/master/FAQ.md#why-two-separate-files-up-and-down-for-a-migration