Oh no, we made a mistake here: Both our json repositories and repo files in /etc/yum.repos.d have the GPG key in a field named `gpgkey`. Unfortunately, cloudapi uses a field named `gpg_key`. One consequence of this issue is that our api.sh test is meant to pass GPG keys in the compose request but since it's using a bad field name (`gpgkey`), the key is actually not used. I've decided to fix this in cloudapi: The `gpg_key` field is now renamed to `gpgkey`. This is a breaking change but no one is using this API anyway so we think it's better to do this now than introducing weird backward compatible hacks. Signed-off-by: Ondřej Budai <ondrej@budai.cz> |
||
|---|---|---|
| .. | ||
| v2 | ||
| server.go | ||