UX guidelines for cloud API key config component

Description

Research and resolve needed UX guidelines for a UI component into which the administrator of a self-hosted Horizon (or Meridian) instance can paste an API key. This API key will enable the Horizon instance to connect to, and consume, various OpenNMS-branded cloud services.

Acceptance / Success Criteria

  • Guidelines are in line with Feather-DS principles

  • Guidelines account for the UI's canvas being part of an OIA plugin

  • API key can be validated instantaneously, provided cloud services are available

  • After validation, user receives indication of successful connectivity and a list of cloud services that are now enabled in the system

  • Error handling in case of invalid API key

  • Error handling in case of expired API key

  • Error handling in case cloud services are unavailable

  • Error handling in case of problems during behind-the-scenes system configuration (e.g. enabling the plugin, writing config files, writing key files, etc.)

Lucidchart Diagrams

Activity

Show:

Jeff Gehlbach August 17, 2022 at 2:39 PM

ended up running with this on our behalf.

Duplicate

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Sprint

Affects versions

Priority

PagerDuty

Created August 3, 2022 at 9:44 PM
Updated August 17, 2022 at 2:39 PM
Resolved August 17, 2022 at 2:39 PM