Variable Scoping with Library

Legacy Uncategorised
1

I’m not understanding the order of precedence of variable scoping (version 2.0.9.1020). Can someone please explain?

I have a Library that defines:
Variable1: value=“value1” scope: Role:roleA
Variable1: value=“value2” scope: Role:roleA, roleB

I have a machine with roles: roleA, roleB
I have a project (that includes the Library) with steps to run on machines in roles: roleA, roleB

  • When I deploy the project, Variable1=“value1”

How can I get the the project to use Variable1=“value2”?

Thanks!

2

Hi Michael,

I believe we use the “most specific” value for the variable. Is there any way you can scope the value you want to a new role, and add that role to the intended machines?

Regards,
Nick