Repositories
What this screen is for
The Repositories tab is where Fenwave is given access to your Git repositories, and where container image registries are registered. Everything that clones code or pushes an image depends on what is configured here.
Before you start
| To do this | You need |
|---|---|
| See the tab | platform-settings.repository.read |
| Add a repository | platform-settings.repository.create |
| Edit one | platform-settings.repository.update |
| Delete one | platform-settings.repository.delete |
| Revalidate credentials | platform-settings.repository.validate |
| Generate an SSH key | platform-settings.repository.ssh.generate |
| Regenerate an SSH key | platform-settings.repository.ssh.regenerate |
| Remove an SSH key | platform-settings.repository.ssh.delete |
| Manage image registries | platform-settings.registry.create .update .delete .validate |
SSH keys have their own three permissions, separate from repository.update.
Holding update alone is not enough to rotate a key.
Opening it
- Settings › Development
- Select the Repositories tab.
The interface
📸 Screenshot Placeholder: The Repositories tab. Mark: (1) Add button, (2) search field, (3) the Provider column, (4) the authentication-method cell showing “SSH Key”, (5) the revalidate action icon.
| # | Control | What it does | When you’d use it |
|---|---|---|---|
| 1 | Add | Opens the repository dialog | Connecting a new repository |
| 2 | Search | Filters by repository | Larger installs |
| 3 | Provider | Which Git host the repository lives on | Auditing what is connected where |
| 4 | Authentication method | Access token, SSH key, GitHub App, or an existing secret | Diagnosing an access failure |
| 5 | Revalidate | Re-tests the stored credentials against the provider | After rotating a token or key |
Authentication methods
| Method | Use it when | Watch out for |
|---|---|---|
| Access token | Quickest to set up | Tokens expire — a working repository can break without any change on your side |
| SSH key | Long-lived automation | The public key must be added as a deploy key on the provider; Fenwave cannot do this for you |
| GitHub App | Organisation-wide access | Requires the app to be installed on the repositories |
| Existing secret | The credential already lives in the cluster | Fenwave does not manage its lifecycle — rotation is yours |
With SSH, you can either provide your own key or have Fenwave generate one. Generating is usually right: the private half never leaves the platform.
Walkthroughs
Connect a repository with an SSH key
Requires platform-settings.repository.create and
platform-settings.repository.ssh.generate.
- Settings › Development › Repositories, click Add.
- Choose the provider and enter the repository.
- For authentication, choose SSH key, then choose to have one generated.
- Save. Fenwave keeps the private key and shows you the public one.
- Add the public key as a deploy key on the provider. Nothing works until this is done, and Fenwave cannot detect that you have skipped it.
- Back on the row, click revalidate. Only a successful validation proves the connection.
Rotate an SSH key
Requires platform-settings.repository.ssh.regenerate.
- Find the repository and regenerate the key.
- Install the new public key on the provider.
- Remove the old deploy key on the provider.
- Revalidate.
Between steps 1 and 2 the repository cannot be cloned. Do this in a quiet window.
Register an image registry
Requires platform-settings.registry.create.
- On the same tab, add the registry with its credentials.
- Validate it. An unvalidated registry fails at push time, at the end of a build, which is the most expensive moment to find out.
Scenario
A build that worked yesterday now fails at clone.
Nothing changed in Fenwave, which is the clue.
- Settings › Development › Repositories, find the repository.
- Look at the authentication method. If it is access token, the token has most likely expired — tokens are the only method that stops working on their own.
- Click revalidate. The failure message names the cause.
- Issue a new token on the provider, edit the repository, paste it in, save.
- Revalidate again and confirm it passes.
- Re-run the build.
If the method was SSH key and validation fails, check the provider: a deploy key removed during a repository cleanup produces exactly the same symptom.
When it doesn’t work
| Symptom | Cause | How to check | Fix |
|---|---|---|---|
| Clone fails, nothing changed in Fenwave | Access token expired | Revalidate the repository | Issue a new token and update the repository |
| SSH configured but clone is refused | Public key not installed as a deploy key on the provider | Provider’s deploy-key settings | Add the public key, then revalidate |
| Cannot regenerate a key although you can edit the repository | Key rotation needs repository.ssh.regenerate |
Access Explorer | Ask for a role granting it |
| Build succeeds then fails on push | Image registry not validated, or its credentials expired | Validate the registry | Update the registry credentials |
| Repository added, pipeline still cannot find it | Never validated | The row’s validation state | Revalidate before using it |