Unclear type of key needed on 'key' charm setting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph OSD Charm |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When one goes through the charm config.yaml, it is unclear the type of key necessary for the 'key' setting, one has to go through the source code to find which type of key is supported.
This bug is raised in order to bring more visibility to users who want to know what type of key is supported.
As per `hooks/
def import_key(key):
"""Import an ASCII Armor key.
A Radix64 format keyid is also supported for backwards
compatibility. In this case Ubuntu keyserver will be
queried for a key via HTTPS by its keyid. This method
is less preferrable because https proxy servers may
require traffic decryption which is equivalent to a
man-
keyserver TLS certificates and has to be explicitly
trusted by the system).
:param key: A GPG key in ASCII armor format,
:type key: (bytes, str)
:raises: GPGKeyError if the key could not be imported
"""
I believe the 'param' describes what we want to put on config.yaml for better visibility.
Changed in charm-ceph-osd: | |
status: | New → In Progress |
Changed in charm-ceph-osd: | |
milestone: | none → 21.10 |
Changed in charm-ceph-osd: | |
status: | Fix Committed → Fix Released |
Reactive charms will carry this description provided by the 'apt' layer - https:/ /git.launchpad. net/layer- apt/tree/ config. yaml#n22