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
support arbitary mountpoints for puppet url's #29
Conversation
the regex also checks out for
|
This pull request was based off an issue in the original repo owned by rodjek, and satisfies the objectives they intended for that issue rodjek#568 There is some discussion of the change in an issue they mention in the description |
Also see conversation at https://puppetcommunity.slack.com/archives/C0W298S9G/p1634939379045200 |
Changing the plugin name (I forgot to change the filename BTW) was a bad assumption on my part. If that's the breaking change, then I don't think that would be necessary. The plugin still validates that a |
I don't think I'm a fan of changing this particular check like @rnelson0 suggests. But if you created a second check with this functionality, I'd be 👍 for it. |
@binford2k can you point me in the right direction where those modifications need to be made? I have no familiarity with the code base, and the pull request you see is literally the first ruby I've edited. I can pick up on the layout of the code and make similarly small changes within an already well defined structure. If it requires a large project, I might not be your guy in the short term |
Moving the files after your change to new filenames and then restoring the original files unchanged would go a long way. |
I'm going to close this PR given that there have been some significant changes to the code and there was no response to the last comment. We really appreciate your contribution & if you would still like to see these changes in puppet-line, please do raise another PR. |
I tested the regex's against these values
I'm not familiar with RSPEC, so I tried to follow the structure of what was there