From 2ba7b984e14817b49c7175b0274e1ec8dd183b34 Mon Sep 17 00:00:00 2001 From: Dan Callaghan Date: Apr 09 2018 01:14:10 +0000 Subject: [PATCH 1/2] .gitignore build directory --- diff --git a/.gitignore b/.gitignore index ed6e30b..7ea6fb3 100644 --- a/.gitignore +++ b/.gitignore @@ -6,6 +6,7 @@ conf/settings.py *.sqlite *.egg* .cache +/build/ docs/_build /rpmbuild-output/ *.src.rpm From 2f1fda237cb0779d305342486599f89384d0cf49 Mon Sep 17 00:00:00 2001 From: Dan Callaghan Date: Apr 09 2018 01:14:10 +0000 Subject: [PATCH 2/2] docs: no need for roadmap We've ticked off all these items now! --- diff --git a/docs/index.rst b/docs/index.rst index 4a92168..68ee1b2 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -11,8 +11,6 @@ test results. developer-guide api release-notes - todo - Indices and tables diff --git a/docs/todo.rst b/docs/todo.rst deleted file mode 100644 index fe51fa5..0000000 --- a/docs/todo.rst +++ /dev/null @@ -1,42 +0,0 @@ -Roadmap -======= - -This describes some plans for the future of WaiverDB. Items are listed in -approximate order of importance. - -Using WaiverDB --------------- - -Currently there is no easy way to actually *use* WaiverDB as a user submitting -waivers. Ultimately we envisage that the consuming tools (for example, Bodhi) -will include some user interface elements to create new waivers in the same -place where they show the failing test results. However as a stop-gap there is: - -* #82: Provide a command-line interface to submit waivers - -There is one additional wrinkle. WaiverDB deployments running in OpenShift -cannot use Kerberos authentication, because clients mostly default to -``dns_canonicalize_hostname=true`` which is fundamentally incompatible with how -OpenShift routes traffic to applications. In that case, something like SSL -certification authentication will need to be used instead: - -* #76: Support SSL certificate authentication - -But we can't reasonably expect end users to obtain an SSL certificate for -submitting waivers, so we will need the consuming tool (Bodhi or equivalent) to -make the request to WaiverDB on behalf of the real human user. In that case -WaiverDB will need to trust the calling service to tell it who the real human -user was: - -* #77: Allow "proxy user" waiving for a configured list of "super users" - -Results may be absent ---------------------- - -One situation we anticipate is that a gating point is being held up a slow test -system or an outage in the infrastructure. In some cases (for example, shipping -urgent security advisories) humans may decide that it is worth the risk to -bypass the test requirement *even if there is no result yet*. - -* #80: Ability to waive the absence of a result -* #81: Ability to waive all results