Postponed
Project:
Hostmaster (Aegir)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Apr 2011 at 20:23 UTC
Updated:
9 Oct 2013 at 12:09 UTC
It would be useful to be able to:
That should be sufficient for most use-cases, as application-specific code could take it up from there.
Comments
Comment #1
steven jones commentedI'm not sure we want to turn Aegir into a MySQL manager, so I'm marking as 'won't fix'. Please provide compelling reasons to re-open if you do :)
Comment #2
helmo commentedOne use-case for creating empty databases would probably be: #1044678: alien platform support
I agree with @Steven Jones that handling root passwords work for a MySQL manager application.
Comment #3
ergonlogicI'm re-opening this, because as helmo mentioned #1044678: alien platform support would benefit from this. But marking 'postponed' since it shouldn't be a priority until after Aegir 2 is released.
'root' was a mistake. I updated the description to better reflect what could be useful here.
Comment #4
j0nathan commented#2107349: obsolete databases housekeeping could be related to this feature request.
Comment #5
helmo commentedLet's generalize the title here...
What would we need:
* a content type to represent a database
** name
** server ID
** optional: resource usage (x MB storage)
* a listing of databases (views integration)
* the current text field on a site node could become an entity reference
* separate provision task to create / verify(update) / delete
* refactor db code to match
* create a queue?
** possibly integrating #2072267: Change site database password?
Not sure if there is enough motivation (developer time) to get this done... but it sounds cool.
Comment #5.0
helmo commentedupdating description