Project

General

Profile

Story #1645

remove enumeration restriction on environment data type

Added by Rob Nahf over 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
d1_schemas
Target version:
Start date:
Due date:
% Done:

100%

Story Points:
Sprint:

Description

We decided that the production nodelist should not contain useful information about non-production contexts, so the environment tag is only useful outside of the production setting. Given this situation, it is more useful to have an uncontrolled list of values instead of the fixed list contained in the current enumeration. For example, environment="nahf-local-testbed-1", "nahf-local-testbed-2".

History

#1 Updated by Rob Nahf over 13 years ago

  • Category set to d1_schemas
  • Priority changed from Normal to High

#2 Updated by Dave Vieglais over 13 years ago

  • Position set to 2
  • Target version changed from Sprint-2011.23-Block.3 to Sprint-2011.26-Block.4
  • Position deleted (2)

#3 Updated by Dave Vieglais over 13 years ago

  • Milestone set to None
  • Assignee set to Rob Nahf
  • Target version changed from Sprint-2011.26-Block.4 to Sprint-2011.33-Block.4

Is this still relevant?

#4 Updated by Dave Vieglais about 13 years ago

  • Status changed from New to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)