Currently if you change the labels set in your playbook and the runner was already installed & registered this role will not update the labels on the server.
Current workaround: Use reinstall_runner: true, but this does more than is really needed. We don't need the runner software to be reinstalled at this point.
Proposed solution: Search the already collected registered_runners.json object for the labels of the already registered runner and compare against runner_labels variable. If they are different use an api call to update the labels.
Summary
Currently if you change the labels set in your playbook and the runner was already installed & registered this role will not update the labels on the server.
Current workaround: Use
reinstall_runner: true, but this does more than is really needed. We don't need the runner software to be reinstalled at this point.Proposed solution: Search the already collected
registered_runners.jsonobject for the labels of the already registered runner and compare againstrunner_labelsvariable. If they are different use an api call to update the labels.Issue Type
Feature Idea