- Issue created by @steven jones
- 🇬🇧United Kingdom steven jones
This happens because Aegir checks in the validation step of the form to see if the publish path is a duplicate, but Aegir Platform Git changes the publish path in the submit step, thus essentially bypassing this check.
- 🇬🇧United Kingdom steven jones
I've marked this issue as critical because anyone who has platforms that end up in this state will need to be extremely careful that they don't migrate sites between them or delete the platforms etc.
- 🇬🇧United Kingdom steven jones
Given the lifecycle of Aegir in general, I'm going to fix the common way that this can break, specifically, where the full publish path matches another platform, but isn't correctly validated by this module.
But there are other, more subtle ways to break things here I suspect, like picking the same path for the root of the repo, but changing the docroot. Then it'll let you make that platform, but presumably do odd things like try to delete it etc.?
- Merge request !3Add a form validation step to check that platforms have unique paths. → (Merged) created by steven jones
-
steven jones →
committed f427fd57 on 7.x-3.x
Issue #3486469 by steven jones: Add a form validation step to check that...
-
steven jones →
committed f427fd57 on 7.x-3.x