-
Notifications
You must be signed in to change notification settings - Fork 108
staging doesn't work on puppet 2.7 on windows #26
Comments
I'm not sure the root cause for the first one, but sounds similar to this post: https://groups.google.com/forum/#!msg/puppet-users/zXpgBB9cZgE/3h1aSJvCNKgJ The second might be addressed by #25. Sorry the Windows feature/PR is not something I'm able to review very well since it's not a platform I use/test. I'll trust the collective input from @reidmv and other users. |
#25 does address the second error. For the first error, yes, we should probably remove the mode parameter when operating on Windows. I'll submit a pull request shortly. Talking to Josh Cooper about whether or not it would be best to leave everything undef or explicitly set owner/group using well-known (static) SIDs to Administrators / Local System. PR will happen once I get that figured out. |
I've created a branch at https://github.com/reidmv/puppet-module-staging/compare/fix_windows_mode. I haven't had time to test it, but if it works I think it's the way to go. |
Tested and merged #33. |
in https://github.com/nanliu/puppet-staging/blob/master/manifests/params.pp
lines 20-22 the mode, group and owner are defined which breaks folder permissioning and creates C:\ProgramData\staging but nothing can write or access it.
error I get:
If I try to set a staging directory by using
target =>
in staging:file I get a different error:@nanliu Is this a known issue for older versions of puppet for Windows? Does this work in the current version?
cc: @rismoney @jumanjiman
The text was updated successfully, but these errors were encountered: