chef / chef/chef-server

Feature Request: Implement requirements check

Open
#4 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect: UX Triage: Confirmed Type: Enhancement
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

Building upon this PR: https://github.com/opscode/opscode-omnibus/pull/104

There are several things that need to be correct/implemented on a server before we can install Chef Server. Currently there is no pre-flight or requirements check. This often results in unclear error messages and undelightful install process. Particularly in secure environments.

Please implement checks for the items in the requirement doc: https://docs.getchef.com/server/install_server_pre.html

Additionally, we should test if the Chef Server is in an offline or proxy mode, and needs additional config to reach the internet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing PR #104 and the linked Chef Server installation requirements document. Identify the required pre-flight checks and the additional offline or proxy configuration checks; the work is done when installation reports clear failures for unmet requirements and handles those network modes.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.