PlanetScale has a quite extensive and elaborated post; Using the PlanetScale CLI with GitHub Actions workflows.
It describes a process used for using multiple (database) branches, which may not be relevant to implement for a two-week exploratory school project. But it does some samples of connection strings that are useful.
You can also explore the .devcontainer folder in this repo - somehow both mysql and pscale CLIs are working fine from the Codespace. It's the .devcontainer/postCreate.sh that does the trick - you can do the same in any GitHub Action runner - which means that you do run any sql scritp agains the database - from your workflow.
I also created a very simple python script: py/dbdump.py I use it to dump the DDL (schema) of a database. But you can easily make a copy - and have it make something else with your remote database. Consequently you not even need mysql or pscale in you GitHub Action Runner?
PlanetScale has a quite extensive and elaborated post; Using the PlanetScale CLI with GitHub Actions workflows.
It describes a process used for using multiple (database) branches, which may not be relevant to implement for a two-week exploratory school project. But it does some samples of connection strings that are useful.
You can also explore the
.devcontainerfolder in this repo - somehow bothmysqlandpscaleCLIs are working fine from the Codespace. It's the.devcontainer/postCreate.shthat does the trick - you can do the same in any GitHub Action runner - which means that you do run any sql scritp agains the database - from your workflow.I also created a very simple python script:
py/dbdump.pyI use it to dump the DDL (schema) of a database. But you can easily make a copy - and have it make something else with your remote database. Consequently you not even needmysqlorpscalein you GitHub Action Runner?