After solving #2821401: Clients can select unavailable platforms during site creation, it might be an idea to have the hostmaster profile automatically created as a locked platform. This would prevent user from accidentally creating a site on it.

Another solution would be to exclusively designate it to admin clients by default, but that checks seems not to be working either.

CommentFileSizeAuthor
#6 lock_the_hostmaster-2821402-6.patch3.5 KBhelmo
#5 create_the_hostmaster-2821402-5.patch1.34 KBhelmo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Neograph734 created an issue. See original summary.

Neograph734’s picture

Neograph734
he/him
Location Netherlands
CreditAttribution: Neograph734 as a volunteer commented
Issue summary: View changes
Neograph734’s picture

Neograph734
he/him
Location Netherlands
CreditAttribution: Neograph734 as a volunteer commented
Issue summary: View changes
Neograph734’s picture

Neograph734
he/him
Location Netherlands
CreditAttribution: Neograph734 as a volunteer commented
Status: Active » Closed (works as designed)

After creating the patch for #2821401: Clients can select unavailable platforms during site creation, it turns out the hostmaster profile is already hidden for regular clients. So there is no need for this.

helmo’s picture

helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions for Aegir Cooperative commented
Title: Create the hostmaster profile as a locked profile by default? » Lock the hostmaster platform by default?
Category: Task » Feature request
Status: Closed (works as designed) » Needs review
FileSize
create_the_hostmaster-2821402-5.patch1.34 KB

This is actually not such a strange idea,

This patch is also in https://github.com/aegir-project/provision/pull/11 , see
https://github.com/aegir-project/provision/pull/11/commits/7ff825a21f99d...

helmo’s picture

helmo CreditAttribution: helmo as a volunteer and at Initfour websolutions for Aegir Cooperative commented
FileSize
lock_the_hostmaster-2821402-6.patch3.5 KB
memtkmcc’s picture

memtkmcc CreditAttribution: memtkmcc at Omega8.cc commented

+1 from me. We are doing this in BOA for years, albeit with direct SQL:

drush @hm sqlq "UPDATE hosting_platform SET status=-1 WHERE nid=7"

Neograph734’s picture

Neograph734
he/him
Location Netherlands
CreditAttribution: Neograph734 as a volunteer commented
Status: Needs review » Needs work

I cannot get this to work on a new install (did not yet test migrate).

I started with a clean vm, and installed all requirements.
Then I ran drush dl --destination=/var/aegir/.drush provision-7.x-3.x-dev to obtain the very lastest provision (7.x-3.8+11-dev).
I patched the files in /var/aegir/.drush/provision
I cleared drush cache
I ran drush hostmaster-install.

Installation completes as expected, but the profile is not locked.

(Perhaps this issue should be moved to the provision project as it took me quite some time to figure out where to apply the patch?)