Open hkirsman opened 1 month ago
Is it important to you to have snapshots with the same name and different database types?
For some time yes until this is still in branch and not yet in main. I would then be ableo to continue working with other features until that's merged. I guess it's an edge that doesn't happen that often. But I think in any case the error message should be better.
I do confirm your results:
Is there an existing issue for this?
Output of
ddev debug test
Expand `ddev debug test` diagnostic information
``` I don't think for the current issue this is not needed but I'll send it if you really need it. ```Expected Behavior
I have snapshot main-mariadb_10.4.gz . When I delete my local env, switch from mariadb to mysql in config.yaml and try to create snapshot, it should be able to do so because there's no main-mysql_10.4.gz snapshot yet.
Actual Behavior
I'm greeting with incorrect error: Failed to snapshot example.com: snapshot main-mysql_8.0.gz already exists, please use another snapshot name or clean up snapshots with
ddev snapshot --cleanup
That file does not exist. So I guess it only checks for the snapshot name itself, then generates the error based on current setup.
Steps To Reproduce
Create snapshot
ddev snapshot --name main
Export your database
ddev export-db --gzip=false --file=main.sql
(without gzip because maybe it's a bit faster :) )Destroy the old env ddev delete --omit-snapshot --yes
Switch to the new mysql db in config.yaml:
Init the new env:
ddev start
Import DB dump. ddev import-db --file=mysql8-tmp.sql
Try to create snapshot again:
ddev snapshot --name main
Anything else?
No response