Script the re-creation of all needed test user accounts and passwords for git6site

i'll have to script their creation into the jenkins job that rebuilds the instance. won't be too terribly difficult.

I created these by hand for the time being so you can continue working. I'll leave the issue open so Sam can automate it since that would be much more awesome.

Let's have this issue track both the Jenkins scripting job for re-creating the users|passes after each git6site restore, and the discussion and documentation of what those test user accounts should be and what they are allowed to do and where they are published.

#1705566: Write Feature File/s for Project issues(your_issues.feature) can then remain focused on it's original objective.

Assigning to @eliza411 temporarily for generation of a private, team-shared list of all users & passes, then back to @sdboyer for the Jenkins piece.

got this mostly scripted, but one important note - that matrix does not include a user whose git permissions have been disabled. we've never had to use that functionality, but it's there, so we need to make sure it works. so, i've added a 'git disabled' user, as well.

when eliza411 added these, she named the vetted user 'git vetted user' instead of 'git vetted', so i'm using that.

also note that git usernames weren't listed here, but are important. as we do not allow git usernames to have spaces, i've just removed the spaces from them. so that means, 'admintest', 'gituser', and 'gitvetteduser'.

finally, we need to file an issue against drupalorg to make some modifications that permanently reserve those [git] usernames, so that we never will have a problem with suddenly having to change EVERYTHING because some unwitting (or devious) person claims those names.

xpost

fyi, i'm running the rebuild job again with the additions that should create & configure these users in an automated fashion. we'll see how well it all works out.

Looks like it's working fine except that git user, git vetted user, and admin, all of whom have agreed to the terms of service, don't have a git user name set, which causes the sole authenticated git test (features/repos.git) to fail. I manually set the username to ensure that's the only problem, and it is.

I've put the passwords into a google doc that can be shared with anyone running tests:
https://docs.google.com/document/d/1ZKR5mqkz3Tc2wFYbDNlV1SgA0oX5hryFA_xK... People can request access via the link or by contacting any maintainer of doobie.

Is there an agreement/awareness statement that people should be reading when they're granted access so they know what they're not supposed to do with data?

@sdboyer We need to be sure that we get the Git instructions URLs to reflect the appropriate host and port, etc. for the server it's on. I know you were trying to set this and having trouble with it. If we need to change the way this is handled by Project git instructions, we should file an issue so helmo can look into a change.

Values on http://git6site.devdrupal.org/admin/settings/project-git-instructions look like:
Repository URL for Authenticated Users:
ssh://@git_username@git6.devdrupal.org:2020/project/@project_name

Repository URL for Anonymous Users:
ssh://git6.devdrupal.org:2020/project/@project_name

Repository URL for Authenticated Users (Sandbox):
ssh://@git_username@git6.devdrupal.org:2020/sandbox/@project_username/@project_name

Repository URL for Anonymous Users (Sandbox):
ssh://git6.devdrupal.org:2020/sandbox/@project_username/@project_name

[Edit: There were two double @ symbols that needed to be single. The above should be correct.]

Thanks for the passwords.
Creating a Sandbox project with Git vetted User is not possible now. Is the permission like this or anything missing for git vetted user?

ach, error in my script around the git usernames. fixed now, should work after the next rebuild.

Does this still need testing?

this is tested and working.