You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so thatI can easily distinguish them and have confirmation that APS team has made necessary updates.
Gateways have a number of attributes which can be customized to allow special functionality, specifically, permitted domains (to allow restricted or custom domains), gateway data plane (to use Gold or Emerald), permitted upstream (controlling which OpenShift projects on Emerald a team can send traffic to), and permitting private/local cluster routes. Currently these attributes must be set by the APS team.
NB: Before actioning this ticket, we must decide if we are looking to change any of these policies to allow direct user control (see https://dpdd.atlassian.net/browse/APS-3140). If that's the case, then we probably want to add UI for controlling some of these attributes (e.g. selecting a data plane), in addition to displaying the attributes. We also need not show permitted domains if they are no longer restricted.
Planning decisions (to refine AC)
decide which attributes to show and on which pages/components (Gateways list, details, dropdown selector)
decide if the default policies will be shown (e.g. show Silver data plane?)
Design
design is required for the UI, ideally using existing components. Could be simple badges
A/C
Gateway attributes are visible on appropriate pages/components
The text was updated successfully, but these errors were encountered:
API Services Portal Issue
User Story
As a API provider,
I want to see key attributes for my gateways
so that I can easily distinguish them and have confirmation that APS team has made necessary updates.
Gateways have a number of attributes which can be customized to allow special functionality, specifically, permitted domains (to allow restricted or custom domains), gateway data plane (to use Gold or Emerald), permitted upstream (controlling which OpenShift projects on Emerald a team can send traffic to), and permitting private/local cluster routes. Currently these attributes must be set by the APS team.
NB: Before actioning this ticket, we must decide if we are looking to change any of these policies to allow direct user control (see https://dpdd.atlassian.net/browse/APS-3140). If that's the case, then we probably want to add UI for controlling some of these attributes (e.g. selecting a data plane), in addition to displaying the attributes. We also need not show permitted domains if they are no longer restricted.
Planning decisions (to refine AC)
Design
A/C
The text was updated successfully, but these errors were encountered: