AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing chef/ohai in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewohai **Umbrella Project**: Chef Infra **Project State**: Active **Issues Response SLA**: 10 business days **Pull Request Response SLA**: 10 business days Description Ohai detects data about your operating system. It can be used standalone, but its primary purpose is to provide node data to Chef. Ohai will print out a JSON data blob for all the known data about your system. When used with Chef, that data is reported back via node attributes. Chef distributes ohai as a RubyGem. This README is for developers who want to modify the Ohai source code. For users who want to write plugins for Ohai, see the docs: • General documentation: • Writing Ohai Plugins documentation: Development Environment Ohai's development dependencies should be installed with bundler. Just run in the root of the repo. Spec Testing We use RSpec for unit/spec tests. To run the full suite, run: You can run individual test files by running the rspec executable: Style We use Cookstyle, as a code linter), to enforce style guidelines. To run: You can run and automatically correct the issues: Rake Tasks Ohai has some Rake tasks for doing various things. Links Source: • Issues: • Contributing For information on contributing to this project see • Fork it • Create your feature branch (git checkout -b my-new-feature) • Commit your changes (git commit -am 'Add some feature' --signoff) • Run the tests • Run the style tests • Push to the branch (git push origin my-new-feature) • Create new Pull Request Auto-merge and required checks This repository has GitHub auto-merge enabled. To help your PR merge quickly: • Keep your branch up to date. GitHub may prompt you to update your PR branch; please do so to keep checks current. • All checks must be green before auto-merge can complete. A workflow named verifies that every configured workflow has passed. • Buildkite must be green. A required Buildkite check blocks merging if it is not successful. • DCO is required. Ensure commits are signed off (use ). License Ohai - system information application • Author:: Adam Jacob (adam@chef.io) • License:: Apache License, Version 2.0 Copyright See COPYRIGHT.md.