570c6d2fee## Problem * #3274 added support for multiple SSH public keys (for `root` and the first user). * You can use `sshPublicKey` (backward compatibility reasons) or `sshPublicKeys`. * However, the `sshPublicKeys` alias does not work (it uses `ssh_public_keys` instead). ## Solution Use the correct alias. ## Testing - *Tested manually* |
||
|---|---|---|
| .. | ||
| .cargo | ||
| agama-autoinstall | ||
| agama-bootloader | ||
| agama-cli | ||
| agama-files | ||
| agama-hostname | ||
| agama-iscsi | ||
| agama-l10n | ||
| agama-lib | ||
| agama-locale-data | ||
| agama-manager | ||
| agama-network | ||
| agama-proxy | ||
| agama-s390 | ||
| agama-security | ||
| agama-server | ||
| agama-software | ||
| agama-storage | ||
| agama-storage-client | ||
| agama-transfer | ||
| agama-users | ||
| agama-utils | ||
| etc/agama.d | ||
| package | ||
| po | ||
| share | ||
| suseconnect-agama | ||
| test/share | ||
| xtask | ||
| zypp-agama | ||
| .gitignore | ||
| build_pot | ||
| Cargo.lock | ||
| Cargo.toml | ||
| install.sh | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
| WEB-SERVER.md | ||
Agama Server
According to Agama's architecture this project implements the following components:
- The Agama server, excluding Agama YaST which lives in the service directory.
- The Agama D-Bus service.
- The Command Line Interface.
Code organization
We have set up Cargo workspace with three packages:
- agama-lib: code that can be reused to access the Agama D-Bus API and a model for the configuration settings.
- agama-cli: code specific to the command-line interface.
- agama-settings and agama-derive: includes a procedural macro to reduce the boilerplate code.
- agama-locale-data: specific library to provide data for localization D-Bus API
- agama-server: implements the HTTP/JSON (and WebSocket) API. Additionally, it offers a minimal D-Bus API for internal communication.