.nc.config.js overrides when adding new provider details through --init flag

Open
#15 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
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
cli, cloud

Research direction

Start by locating the --init entry point and the handling of .nc.config.js. Reproduce the provider-details flow to determine how existing configuration is overwritten, then inspect the related CLI tests if present. Done means adding provider details through --init no longer unexpectedly overrides the configuration.

Written by the indexing model from the issue text.

Description

bug Hacktoberfest

This issue has no description.

Dominant language
JavaScript
Stars
29
Forks
31
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 leopardslab/nodecloud-cli

All issues in leopardslab/nodecloud-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.