Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix disable_<tag-name> config option #42567

Merged
merged 1 commit into from
Jul 27, 2017
Merged

Conversation

skizunov
Copy link
Contributor

What does this PR do?

Previously, the logic always looked for disable_<tag-name>s in
the config options. The issue with this is that the following tag names
already end with 's': beacons, engines, grains, log_handlers,
serializers, states, and utils. So previously, if you wanted to
disable a beacon, the config option to set is disable_beaconss (with
'ss' at the end). Fix this so that we only append an 's' if the tag name
does not already end with an 's'.

Tests written?

No

Previously, the logic always looked for `disable_<tag-name>s` in
the config options. The issue with this is that the following tag names
already end with 's': `beacons`, `engines`, `grains`, `log_handlers`,
`serializers`, `states`, and `utils`. So previously, if you wanted to
disable a beacon, the config option to set is `disable_beaconss` (with
'ss' at the end). Fix this so that we only append an 's' if the tag name
does not already end with an 's'.

Signed-off-by: Sergey Kizunov <sergey.kizunov@ni.com>
@ghost
Copy link

ghost commented Jul 26, 2017

@skizunov, thanks for your PR! By analyzing the history of the files in this pull request, we identified @jacksontj, @thatch45 and @s0undt3ch to be potential reviewers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants