-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
active choices: 2.6.4
jenkins: 2.346.3 (I'm on CentOS 6, so this is the latest Java available without custom work)
I just noticed that when I have a set of PT_SINGLE_SELECT (the type of parameter probably isn't important) parameters like:
param: DefaultChoices
param: BaseAMI, with a referencedParameters of DefaultChoices
param: Install, with a referencedParameters of BaseAMI
param: Version, with a referencedParameters of Install.
(they have other referencedParameters, if that is important, but I'm trying to make the simplest case to show the bug)
If I change DefaultChoices, I expect Version to be updated base on Install, which changes based on BaseAMI, which changes based on DefaultChoices.
However, Version isn't changed, though the other two are.
Is there a maximum length of the list of changed items? I'm pretty sure my code is working, and if I change Install or BaseAMI, Version is appropriately changed.
I think I can workaround this by making Version directly dependent on DefaultChoices, but that seems kind of hacky, and prone to bugs if I update another parameter without realizing the impacts on its "children".