Add support for export/import to Gitlab snippets

[joejag]

Feature Request

What would you like to be able to do?

Export and import config to Gitlab in the same manner as Github.

Support both gitlab.com and internal gitlab instances.

Snippets API: https://docs.gitlab.com/ee/api/project_snippets.html

API Examples:

http POST https://gitlab.com/api/v4/snippets?private_token=$PRIVATE_TOKEN \
    title="Nevegreen Config Backup" \
    file_name=nevergreen.json \
    visibility=public \
    [email protected]

http GET https://gitlab.com/api/v4/snippets/$SNIPPET_ID/raw?private_token=$PRIVATE_TOKEN 

http PUT https://gitlab.com/api/v4/snippets/$SNIPPET_ID?private_token=$PRIVATE_TOKEN \
    title="Nevegreen Config Backup" \
    file_name=nevergreen.json \
    [email protected]

Remaining Tasks

Prod code:

• Handle error messages from GitLab
• Update schema to add new GitLab config
• Allow custom hosts to be added to the CSP (similar to iframe)
• Help text
• Mobile styling (issue with tabs overflowing)

[GentlemanHal]

Just wondering out loud, is it worth moving the complexity to the server?

As in we provide a /backup (or whatever) endpoint that just takes the json and a where (or whatever) parameter.

POST /backup
{
    "where": "gitlab",
    "description": "Nevergreen backup",
    "content": {
        ...the json to backup...
    }
}

[GentlemanHal]

FYI, if we do it from the UI we'll need to update the content security policy connect-src to include gitlab.

[joejag]

It's also a bit worse than that @GentlemanHal as if we support internal GitLab servers we will need them to update the server to change the CSP

[GentlemanHal]

It's also a bit worse than that @GentlemanHal as if we support internal GitLab servers we will need them to update the server to change the CSP

Oh, good point! This would be another advantage of having our own API.

[joejag]

Tested with GitLab official.
Going to test with a hosted GitLab.

[joejag]

Tested with a hosted GitLab. All working.

We could improve things by pre-populating the available URLs given the environment variable provided by the user, but given [#271] will make the environment variable redudant I'd suggest we don't do this just now.