Bug 1394044 - Validation of environment variable names is overly strict when editing DC
Summary: Validation of environment variable names is overly strict when editing DC
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Management Console
Version: 3.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 21:39 UTC by Justin Pierce
Modified: 2016-12-09 21:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-09 21:50:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Justin Pierce 2016-11-10 21:39:48 UTC 
Description of problem:
When editing environment variables in the DC->Edit page, environment variables starting with underscores fail validation.
Some environment variables do start with _ . This validation does not appear to take place on the "Environment" tab of the DC which permits environment variables which start with _.

Version-Release number of selected component (if applicable):
3.4.0

How reproducible:
100%

Steps to Reproduce:
1. Create a deployment config
2. On the environment tab, add an environment variable _TEST=1
3. Save your changes
4. Select "Edit" from the DC Actions drop down box

Actual results:
I see a validation error on _TEST

Expected results:
_TEST is a valid environment variable. 


Additional info:
Comment 1 Yadan Pei 2016-11-14 06:33:02 UTC 
Checked against v1.4.0-alpha.1+9c4f9ee-179

Now user could succeed in adding environment variable _TEST=1 on DC Environment Tab & Edit DC page

Move to VERIFIED
Note You need to log in before you can comment on or make changes to this bug.