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 handling for bare-string mapcontents #110

Merged
merged 1 commit into from
Mar 24, 2018

Conversation

jcbollinger
Copy link
Contributor

The data type for the 'macontents' parameters of autofs::mount and
autofs::map permits both arrays and bare strings, and the documentation
is consistent with that, but catalog building failed when a bare string
is assigned to one of these parameters. The bug was in the templates;
these are updated to handle the situation, and a unit test is added to
verify that it works.

Closes #108

The data type for the 'macontents' parameters of autofs::mount and
autofs::map permit both arrays and bare strings, and the documentation
is consistent with that, but catalog building failed when a bare string
is assigned to one of these parameters.  The bug was in the templates;
these are updated to handle the situation, and a unit test is added to
verify that it works.
@juniorsysadmin juniorsysadmin added the bug Something isn't working label Mar 24, 2018
@juniorsysadmin
Copy link
Member

I would have preferred array or string, not allowing both in #95 but that is a breaking change for another day.

@bastelfreak bastelfreak merged commit 719d4e4 into voxpupuli:master Mar 24, 2018
@bastelfreak bastelfreak changed the title Fixed handling for bare-string mapcontents Fix handling for bare-string mapcontents Mar 24, 2018
@bastelfreak
Copy link
Member

Thanks for the patch @jcbollinger !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants