(FM-8422) Make library releasable as a Puppet module #8
Conversation
michaeltlombardi
changed the title
|
Open question: Do we actually want to do a build + release of a the puppet module including all the cruft here, or do we want a rake task that can clean things up for a much slimmer release (which includes only the library, changelog, appropriate readme, etc, dropping the spec/images/etc). |
| @@ -0,0 +1,86 @@ | |||
| # pwshlib | |||
|
|
|||
| This module enables you to leverage the `ruby-pwsh` gem to execute PowerShell from within your Puppet providers without having to instantiate and tear down a PowerShell process for each command called. | |||
There was a problem hiding this comment.
The forge will still show the regular README.md
There was a problem hiding this comment.
Yeah, I had a think about this last night, this is one of the problems with having it all in one repo.
I think a build task could rejigger things long enough to do a pdk build, then put them back, but I don't think rewriting the main readme to make more sense on the forge is the right move.
|
If you want to slim down the module tarball, have a look at the Either way, as a 0.1.0, this is good enough for me. |
|
Added a |
michaeltlombardi
changed the title
.pmtignore
Outdated
| Gemfile | ||
| Gemfile.lock | ||
| Rakefile | ||
| ruby-pwsh.gemspec |
Prior to this commit the library code could only be released as a ruby gem. This commit adds the necessary metadata and documentation for it to be released as a Puppet module upon which other Puppet modules may depend and thereby use the manager and helpers.
Prior to this commit the library code could only be released
as a ruby gem. This commit adds the necessary metadata and
documentation for it to be released as a Puppet module upon
which other Puppet modules may depend and thereby use the
manager and helpers.