Make system-level configuration optional

Open Beginner friendly
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Start by locating the initConfiguration() function and trace how it handles the system-level configuration file compared with the other configuration layers. Done means the system-level file may be absent without initialization failing, while existing configuration layers continue to work; run the project’s available tests or local CLI initialization checks.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Currently, if the system-level configuration file is not found, the initConfiguration() func will fail. This is OK in the case where the binary is installed in a system-wise fashion (e.g. through a package manager), but not in cases where it is installed locally (e.g. through go install ... or directly from a binary).

We need to make the system-level configuration file optional like all the other layers to facilitate usage with all standard ways.

Dominant language
Go
Stars
29
Forks
12
Avg merge
19h 37m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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.

More from nokia/corteca-cli

All issues in nokia/corteca-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.