-
Notifications
You must be signed in to change notification settings - Fork 4
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
A fileContent resource for simple file contents #5
Comments
Hi @jnury - sure! I would gratefully accept the PR! I have adopted the standard contribution policies and style guidelines of the DSC Resource Kit. |
HI @jcwalker - I'd be grateful for the assist - I've not had much time of late to get DSC stuff done. Regarding the expected behavior: If the Encoding parameter was specified, but it differed from the Encoding on the existing file, would you expect that the file encoding was corrected on the file? I think as a consumer of the resource that a file would be converted to the correct format. |
I agree. I would think if the desired encoding was different than the original file it would be converted. |
Are we agreeing that we should move forward with using the Encoding parameter instead of creating a new resource? I would be happy to own this and could start early next week. |
@jcwalker - absolutely agree! And I'd love the help if you're up for submitting a PR. I haven't had as much time to put into these projects lately (hands full on the DSC Resource kit). |
Awesome - thanks @nehrua |
Hi,
The 'file' resource of PSDesiredStateConfiguration lake the ability to create file in different encodings (ascii, utf8 without bom etc...). I haven't find any DSC resource that propose to create files in ASCII, so I planned to write a new one to just create a file with the specified content and selected encoding.
As the fileContent resource is already here and propose similar functionalities, would-you mind if I create a PR with a new 'fileContent' resource for simple files ?
The text was updated successfully, but these errors were encountered: