Need an external API to use for monitoring and other automation purposes
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Originally the chef sensu plugin used chef/rest to pull information about nodes and the server for monitoring purposes, in chef 13 this was deprecated without a clear successor. As ridley was very stable and used in berkshelf we moved to that but then they deprecated external use. We searched and found https://github.com/sethvargo/chef-api but it indicated it was under heavy development and not production ready so we held off now it has been archived. I spoke with @tas50 about this and he said we should open an issue here to discuss.
Issues:
- https://github.com/sensu-plugins/sensu-plugins-chef/issues/33 (current issue)
- https://github.com/sensu-plugins/sensu-plugins-chef/issues/25 (when we re-wrote from
chef/resttoridley)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked sensu-plugins/sensu-plugins-chef issues and the history of chef/rest, ridley, and chef-api. The issue does not name implementation files, tests, or a defined API scope; completion would require an agreed production-ready external API for monitoring and automation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100