Closed
Bug 1539289
Opened 6 years ago
Closed 6 years ago
Make a revision's security classification first-class API data
Categories
(Conduit :: Lando, enhancement, P2)
Conduit
Lando
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mars, Assigned: mars)
Details
(Keywords: conduit-triaged)
Attachments
(1 file)
A revision's security classification is currently passed between Lando API and UI as part of the set of revision warnings, ultimately intended to control landing sign-off and display to the end-user. If we want to trigger a sec-approval workflow based on a revision's security classification it would be preferable to pass the security classification as an explicit piece of data between the API and UI instead of adding the responsibility of workflow control to the security warning element.
|
||
Updated•6 years ago
|
Keywords: conduit-triaged
Priority: -- → P2
|
Assignee | |
Comment 1•6 years ago
|
||
|
|
Assignee | |
Comment 2•6 years ago
|
||
This has landed on dev and prod.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•