Hide Forgot
Description of problem: While testing configserver and a deployment with variables to auto-register to a running katello instance, sreichar discovered that audrey does not support empty parameters. Specifically, the test involved a deployment with an empty ACTIVATION_KEY variable. While discussing with sreichar and gblomquist, it appears that all parameters are required. This bug is to request support for optional config parameters in a deployable XML. Version-Release number of selected component (if applicable): * aeolus-configserver-0.4.5-2.el6 How reproducible: * 100% Steps to Reproduce: 1. Create a deployable XML with an empty config parameter (e.g. see ACTIVATION_KEY within http://jlaska.fedorapeople.org/katello-register.xml) 2. Attempt to deploy using conductor web-ui Actual results: > On Fri, 2012-01-27 at 16:04 -0500, Steve Reichard wrote: > In a service I was creating to register to katello/candlepin, have have > the situation that I need some variable only if I am not going to use an > activation key and do not need the actiavtion key variable. Likewise, > if I am going to use an activation key I don't need other variables. > > The UI does not appear to let any variable be blank, is this by design? > I was planning to a blank activation key as a sign not us use it, but > that doesn't seem possible. Expected results: The conductor web-ui should allow you to proceed without providing a value for a variable. * Whether specific variables are marked as optional, or all variables accept no value? Additional info: * Requesting as a nice-to-have for cloudforms-1.0.0 (adding qa_ack+ approval)
JRD, I'm inclined to NACK this since it's an RFE and we're in beta, but I'm leaving it up to you.
I concur, this would be nice, but I don't see much downside to deferring it, and I'd like to minimize risk where we can. Moving to 1.1.
Thanks for the feedback gents. I'm adding the release_notes flag so we can document this known issue for v1.0
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: For 1.0, blank values in the Config Server UI are not supported. Users must fill in something for every line.
Release note added: http://documentation-stage.bne.redhat.com/docs/en-US/CloudForms/1.0/html/Release_Notes/chap-Release_Notes-Cloud_Engine.html#sect-Release_Notes-Cloud_Engine-known_issue_12
Active development on Aeolus Configserver has stopped.