| 2017-02-17 14:28:13 |
Andres Rodriguez |
description |
When adding a custom repository, I avoided adding a GPG key. The custom repository was added successfully.
That said, the fact that there was no GPG key could have been a problem, provided it could have deployed.
MAAS should either:
1. prevent adding a custom repo without a GPG key
2. Warn the user about it adding a custom repo without a GPG key |
When adding a custom repository, I avoided adding a GPG key. The custom repository was added successfully.
That said, the fact that there was no GPG key could have been a problem, provided it could have deployed.
MAAS should either:
1. prevent adding a custom repo without a GPG key
2. Warn the user about it adding a custom repo without a GPG key
====
After more investigation, we allow not adding a key, so it should probably do (2) |
|
