Using Git on the Execution Environment
The SSH Key Setup in your user profile enables full Git access on the Execution Environment. Clone, push, pull, commit, and all other Git operations work directly from your Session — with commits attributed to your actual Git user. vHaaS generates an SSH key per Session, registers it with your GitLab or GitHub account, and removes it when the Session ends.
Add an SSH key
Prerequisites
- A Personal Access Token that lets vHaaS read your user and add, list, and delete the SSH keys of your account.
Recommended. Available from GitLab 19.2.
Create a fine-grained token via Generate token → Fine-grained token. Under Add resource permissions, open the User tab and grant:
| Resource | Permissions |
|---|---|
| SSH Key | Create, Read, Delete |
| User | Read |
Both are User resources, so vHaaS needs no group or project access. GitLab requires the Group and project access setting only when you add group and project resources. If it is shown, select Only my personal projects to keep the token as narrow as possible.
Create a token via Generate token → Legacy token with the api scope.
Warning
Legacy tokens grant access to all your groups and projects. If your GitLab administrator enforces fine-grained tokens, legacy tokens are rejected.
Create a fine-grained personal access token with the account permission Git SSH keys set to Read and write.
A classic token with the admin:public_key scope also works.
Steps
1. Open the SSH key setup view
- Click the profile page in the right corner of the Navigation Bar and open the SSH Key Setup view.
2. Create an SSH key
- Click the Add Button in the upper right corner of the SSH Key Table. Fill out the Form and confirm by clicking Add.