Skip to content
This repository was archived by the owner on Feb 15, 2022. It is now read-only.
This repository was archived by the owner on Feb 15, 2022. It is now read-only.

Specifying an config file as a parameter for spk init creates a copy of the file resulting in 2 config files (original + config.yaml) #1226

@andrebriggs

Description

@andrebriggs

Feedback:

In ~/.spk I now have 2 config.yaml files that are exact duplicates, given that spk-config.yaml was passed as a paramter the user is unaware of the other file and this leads to confusion which file to maintain going forward. Consider providing a message back to the user that an "import" of the file was made and that going forward the config file is located at ~/.spk/config.yaml.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingx-projectMapped to external projects

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions