Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions .github/workflows/test-deploy.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,6 @@ name: Test deployment

on:
pull_request:
branches:
- main
# Review gh actions docs if you want to further define triggers, paths, etc
# https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on

Expand Down
43 changes: 34 additions & 9 deletions docs/user/unattended/profile/software.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,23 +4,48 @@ sidebar_position: 2

# Additional software

Depending on the [product you are installing](./product), Agama will select a set of patterns and
packages to install. However, it is possible to add your own list of patterns and packages using the
`software` section.
Depending on the [product you are installing](./product), Agama will select a set of repositories,
patterns and packages to install. However, it is possible to add your own list of repositories,
patterns and packages using the `software` section.

This section supports two keys:
This section supports three keys:

- `patterns`: list of patterns to install (e.g., `gnome`, `kde`, `fips`, etc.). You can find a list
of patterns for your distribution using `zypper se --type pattern`.
- `packages`: list of packages to install (e.g., `neovim`).
- `extraRepositories`: list of additional repositories that will be used as installation source.

```
```jsonnet
{
patterns: ["gnome", "office"],
packages: ["neovim", "emacs"]
packages: ["neovim", "emacs"],
extraRepositories: [
{
alias: "games",
url: "https://download.opensuse.org/repositories/games/openSUSE_Tumbleweed/",
gpgFingerprints: ["AEF1 EE83 0A27 90AB ABC2 CDA2 8F91 B0E6 C862 B42C"]
}
]
}
```

:::note Custom repositories
Adding custom repositories will be supported soon.
:::
## `extraRepositories` Properties

The `software` section allows you to define custom repositories using a list under
the `extraRepositories` key. Each repository in the list can have the following properties:

`alias`: A unique identifier for the repository. Mandatory property.
`url`: The repository's URL, recognized by `libzypp`. Mandatory property.
`priority`: Sets the priority for using this repository. A lower number means higher
precedence. If you don't specify this, it'll use the same default priority as other repositories.
`name` (string): A user-friendly name for the repository. If omitted, it defaults to
the `alias`.
`productDir`: A path to a specific product related to the URL. This is mainly used
for multi-product media and isn't used by default.
`enabled`: Controls whether the repository is active. This is handy for
pre-defining repositories you plan to enable later. By default, repositories are enabled.
`allowUnsigned`: If set to `true`, the repository will be accepted even if it lacks
a GPG signature. This can be useful for your own repositories. It's not set by default.
`gpgFingerprints`: A list of accepted GPG fingerprints for the repository.
This is helpful if the repository is signed by a GPG key not included in your installation medium.
This list is empty by default.