4 Adds tags to roles that allow an operator to specify custom tags to use
5 when trying to find functionality available from a role. Currently a role
6 with both the 'primary' and 'controller' tag is consider to be the primary
7 role. Historically the role named 'Controller' was the 'primary' role and
8 this primary designation is used to determine items like memcache ip
9 addresses. If no roles have the both the 'primary' and 'controller' tags,
10 the first role specified in the roles_data.yaml is used as the primary
14 If using custom roles data, the logic was changed to leverage the first
15 role listed in the roles_data.yaml file to be the primary role. This can
16 be worked around by adding the 'primary' and 'controller' tags to the
17 custom controller role in your roles_data.yaml to ensure that the defined
18 custom controller role is still considered the primary role.