#397 expose backend's default GPG keys via API
Opened 7 months ago by ktdreyer. Modified 5 months ago

As discussed in #389, the backend server has a default list of sigkeys and arches. There is no way for clients to know what is configured on the ODCS backend server. We could add this information to the /api/1/about endpoint.

The purpose of this change is to make ODCS easier to understand so that users can troubleshoot on their own without involving an administrator.


Should arches be exposed or just sigkeys?

As discussed in #389, the backend server has a default list of sigkeys and arches.

I think we should expose all the settings. For example we're already exposing raw_config_urls, and that really helps non-administrators understand what is supported.

Login to comment on this ticket.

Metadata