In this knowledge article we will demonstrate how to utilize Mission Control integration with VCS providers in order to externalise and pull Mission Control User configuration scripts.
* The particular Git provider that will be shown here is Github.
As Mission Control support git protocol and includes integration with VCS system, this functionality will allow you to manage versioning sharing and collaboration Mission Control configuration scripts in easy platform such as GitHub and Bitbucket.
When working with Git server you will need to identify yourself to Git server, use either one of the ways below to do so:
Connection to the Git server with credentials.
Connection to the Git server by SSH keys.
For SSH authentication with GitHub: SSH keys come in pairs, a public key that gets shared with service, and a private key that is stored only on your computer. If the keys match, you can access to the account.
The cryptography behind SSH keys ensures that no one can reverse engineer your private key from the public one.
To create an SSH connection between your GitHub user to Mission Control follow this step by step guide:
1. Use the following command to create the keys and add your email address:
$ ssh-keygen -t rsa -b 4096 -C "email@example.com"
2. Enter the filename to save the key files the default directory is (users/<user>/.ssh/id_rsa)
* Please note that for JFMC Git integration the ssh MUST be saved under your .ssh/ folder
3. Click on the setting button on your Github profile as the following screenshot :
4. Click on new SSH key as the following screenshot :
5. Add your id_rsa.pub input into the new ssh key and paste a title as the following screenshot :
6. In Mission Control under version control enable git integration and add the Github SSH URL for example:
7. Open your Mission control under version control tab insert the SSH url of your GitHub project as the following screenshot:
8. After clicking the Ok button, add the master branch as mentioned in our Wiki page. Please note that you may only work with the master branch and it must exist before being configured in Mission Control as the following screenshot:
* In case you have created Mission Control scripts before the Git integration, those scripts will not push to the VCS server. On the other hand when you already enabled Git integration and creating a new Mission control script the scripts will update and create in the VCS server too.