Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 959035

Summary:	Make beaker-wizard configurable
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	wizard	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	0.12	CC:	cbouchar, isenfeld, mjia, ohudlick, qwan, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-19 22:02:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Coghlan 2013-05-03 03:37:39 UTC

Beaker-wizard currently hard codes several Red Hat specific elements, notably:

1. The default licenses
2. The list of test types
3. The list of namespaces
4. The list of releases
5. The specific Bugzilla instance (via the URL settings)
6. The default user preferences

The core list of test types can be simplified to just Regression and Security, as they're needed by the bugzilla integration (which uses Regression by default, unless given a CVE number). The default (unconfigured) test type would be Regression.

The core list of namespaces can be simplified to just one (distribution, for Beaker provided tests). 

I'm not quite sure what to do about the releases - what's there now is probably a reasonable fallback for as long as Beaker provisioning remains anaconda specific.

Comment 2 Nick Coghlan 2013-05-03 03:56:48 UTC

For bonus points, it would be helpful if optional site specific URLs (or just extra help text) could be configured that are presented when asking users to choose a license, test type, namespace and release.

These are the kinds of things that are really going to be dependent on the specific installation, so the best we can do from a UI point of view is make it easier for those operating the instance to point their users in the right direction.