updating REST api with multiple gpg keys support, due backwards compatibility introducing CSV under same key (gpg-key)

This commit is contained in:
Ales Bregar
2025-08-12 17:58:45 +02:00
committed by André Roth
parent 9b523e6bd5
commit 12604b9379
2 changed files with 22 additions and 4 deletions

View File

@@ -25,7 +25,11 @@ Public part of the key should be exported from your keyring using `gpg --export
```
aptly publish repo my-repo --gpg-key=KEY_ID_a --gpg-key=KEY_ID_b
```
* If `--gpg-key` is specified on the command line, it takes precedence over any gpgKeys configuration in `aptly.conf`.
* When using the REST API, the `gpgKey` parameter supports a comma-separated list of key IDs:
```
"gpgKey": "KEY_ID_a,KEY_ID_b"
```
* If `--gpg-key` is specified on the command line, or `gpgKey` is provided via the REST API, it takes precedence over any gpgKeys configuration in aptly.conf.
* With multi-key support, aptly will sign all Release files (both clearsigned and detached signatures) with each provided key, ensuring a smooth key rotation process while maintaining compatibility for existing clients.
#### Parameters