-
Basically a copy-paste job that puts any code in `providers` directly in to the corresponding file in `resources`. There will probably be some tweaks along the way.
I can do this if maintainers are…
-
It looks like even if the install using the LWRP fails, Chef reports success on completion. On the next run the install is attempted again. This continues for all subsequent runs.
I ran the same co…
-
Running into an issue where using the nodejs_npm lwrp with a json (packages.json) file will run 'npm install' on every converge.
```
nodejs_npm 'node-app-name' do
path '/path/to/app'
json true
…
-
Add usage information about new LWRP method
-
The docs say that the pool lwrp will use the node's IP and fqdn if nothing is provided. This doesn't work.
-
The section:
``` ruby
service_factory "repairbot" do
service_desc "Cassandra RepairBot"
exec "/opt/repairbot/virtualenv/bin/python /opt/repairbot/repairbot.py"
run_user "root"
run_group "root…
-
The current implementation triggers on every run. It would be fairly simple to resolve this and modernize the implementation by switching to a 12.5 custom resource.
tas50 updated
3 years ago
-
It would be nice if it will be possible to configure pm.status_path via attributes or a pool definition lwrp. Cause right now status is just disabled and it is hardcoded.
-
Every time the LWRP is run it tries to install chef-vault
-
Is it worth considering this for a new project? How does it fare against the LWRP?