[bug] cmdx: config read, write and load behave differently

Open
#58 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start by comparing the cmdx config read, write, and load entry points, including the YAML handling and the salt/config path that uses viper and mapstructure. Reproduce a configuration written with write, then check whether load can read it and whether read displays every set value. Done means these operations handle the same configuration consistently.

Written by the indexing model from the issue text.

Description

config read, write use yaml format while load uses salt/config which internally uses viper and mapstructure for processing configs.

This creates an issue that configs written via write cannot always be properly loaded by load function.
And read doesn't necessarily display all set configs.

Dominant language
Go
Stars
14
Forks
8
No merged PRs in 30d

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 raystack/salt

All issues in raystack/salt

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.